Personally, what I'm doing is to leave my system python completely as it is.
I use the following to install Python versions 2.4, 2.5, and 2.6:
Use buildout from plone collections to get python2. {4,5,6} installed with easy_install and PIL (including libjpeg support)
Checkout python assembly files from plone collections. I like putting it in / home / dev / python -buildout
# svn co http:
Add a new local.cfg file to the src directory. Here you indicate what you want to build. In the assembly file, do the following:
[buildout] extends = base.cfg readline.cfg libjpeg.cfg python24.cfg python25.cfg python26.cfg links.cfg parts = ${buildout:base-parts} ${buildout:readline-parts} ${buildout:libjpeg-parts} ${buildout:python24-parts} ${buildout:python25-parts} ${buildout:python26-parts} ${buildout:links-parts}
Download your system python and then run buildout.
# python bootstrap.py
When everything has been compiled, you should have new python binaries:
/home/dev/python-buildout/src/python-2.{4,5,6}/bin/python
To use them, either add the bin directory to your path, or specify an βactivateβ script in the bin directory, which will set it as active python in your current shell
daniel@madmax
For each project I'm working on, I try to create a new virtual environment using non-package sites and the corresponding version of Python.
source share