jessenoller.com

So, as a fol­lowup to my pre­vi­ous post — PyObjc 2: Leop­ard, Python 2.5.1 and You. A com­menter pointed out that the python.org instal­la­tion of python only adds a new ver­sion of Python to the /Library/Frameworks/ direc­tory — it does not replace the default one in /System/Library/Frameworks/.

So, in order to “return” to my “pris­tine” leop­ard state, all I actu­ally had to do was remove this line in my .bash_profile (which I hadn’t noticed — my .bash_profile is about 250 lines long):

PATH="/Library/Frameworks/Python.framework/Versions/Current/bin:${PATH}"

Then I sim­ply moved the /Library/Frameworks/Python.framework direc­tory to some other name (just to be anal). The only side-effect being that I “lost” all of my installed python mod­ules in the python.org install’s site-packages directory.

The lat­ter is fine, because I’ve been mean­ing to ‘clean house’ with the cruft I’ve built up com­pul­sively down­load­ing stuff from pypi and doing other work. Since I’m now deal­ing with a ‘cleaned out’ ver­sion, I took the chance to clean-install vir­tualenv and setup a nice /jesse/python_vms direc­tory. I added a ‘default’ pro­file that gets auto-loaded on login, and added a few func­tions to let me switch in-between them. Exam­ple:

# Python VMs override(s)
VMDIR="/Users/jesse/python_vms"
DEFAULT_PY_ENV="$VMDIR/default"
SANDBOX_PY_ENV="$VMDIR/sandbox"
# Load the default python env by, uh, default!
. $DEFAULT_PY_ENV/bin/activate
pydefault () { . $DEFAULT_PY_ENV/bin/activate; }
pysandbox () { . $SANDBOX_PY_ENV/bin/activate; }


In my case, the default pro­file will only load my work-profile, while my sand­box is going to be where all the pypi mod­ules I tin­ker with go. The nice thing of course, is that the acti­vate script included with the vir­tualenv env over­rides my default $PATH to make sure the local bin direc­tory is used prior to the main $PATH, which means I don’t need to worry about con­flicts with the default easy_install that comes with Leopard.

Now I’ve got the best of all worlds, the default install that has all the leop­ard pyobjc good­ies, and a nice clean sandbox.

Of course, this doesn’t even cover the hor­ror which is my /subversion direc­tory — which at last look, I had to write a shell-script wrap­per to auto-update the lar­gish num­ber of svn projects I watch/sync.

So, as a fol­lowup to my pre­vi­ous post — PyObjc 2: Leop­ard, Python 2.5.1 and You. A com­menter pointed out that the python.org instal­la­tion of python only adds a new...