Particularly, Python 3.3 got released on 2 after the last commit to the rope_p圓k sourcecode which happened on the 2 (as of 2014). The code seems to be hosted on github, too. #Pymacs rope aquamacs installThen you install Pymacs, from its website. Currently (Jan '16), the github project page has newer versions than PyPi. My ~/.emacs.d/init.The original rope library does indeed support P圓k according to its webpage As a final step, it creates an easy-to-find symlink to the pymacs.el so that my main Emacs file does not have to remember the name of its source directory, which changes with each new version. Without having to assume an elevated privilege even once, this script removes any old virtualenv sitting in the way, builds a new one, and installs the four Python packages into it. done # Make fresh pymacs.el symlink from ~/.emacs usr $ do cd $D python2.5 setup.py install cd. cd $(dirname "$0" ) # Clean up directories left over from previous run. ![]() # Brandon's ~/.emacs.d/src/build.sh # Change to the directory containing this script. tar.gz archives of the Python packages that I want Emacs to use: Here is the real-life build.sh shell script (yes, I am old-fashioned) that I keep in version control along with the. I always simply include a copy of virtualenv in the files that I push to a new home directory whenever I get a new account somewhere. #Pymacs rope aquamacs archiveWhenever you run the easy_install and python commands that virtualenv has created under this new directory, they will install packages to, and load packages from, the site-packages directory sitting right there in the virtual environment with them.īut how, you ask, does the virtualenv command itself get installed? Doesn't that, at least, require root access to easy_install? Not at all! The command is entirely self-contained just grab the virtualenv.py file from inside of the virutalenv tar archive on its page at the Python Package Index. emacs / usr / bin / python / home / bcr /. emacs / usr / bin / easy_install / home / bcr /. #Pymacs rope aquamacs upgradeEven better, packages that I install or upgrade inside of the virtual environment cannot interfere with Python programs running elsewhere on the system.Ī “virtual environment” is a little self-contained Python install, whose essential files are copied from your main system Python no additional compilation is necessary! A virtual environment can be created under any directory on your system.įor example, on a Unix system, the default Python probably lives under the /usr directory, and looks like this: The virtual environment lives under my own account, and is easy to create, access, and rebuild, even in the absence of root privileges on a particular machine. Although my setup is probably too simple to be interesting as a public project, there is one aspect of it that I should share: unlike Ryan, I use the advanced technology of a virtualenv to hold the Python packages that Emacs needs. Like Ryan, I also keep my Emacs configuration under version control, so that improvements I check in from one account are easy to check out into all of my other accounts. This means that his Emacs configuration - which, very generously, he has started maintaining as a project on github so that other people can use it themselves, or branch their own versions - requires root access merely to install. The only rough edge I have found amidst the otherwise exceptional advice on Ryan McGuire's Enigma Curry blog is that Ryan recommends installing Python packages with: Simply visit my dot Emacs repository on GitHub at the following URL: ![]() Not just the little snippet that is shown in this old blog post. ![]() #Pymacs rope aquamacs updateUpdate - my entire Emacs configuration is now public,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |