Maybe you should look http://pypi.python.org/pypi/pythonbrew/ instead. When I did it, I used pythonbrew to create the venv
pythonbrew install 2.7.3
pythonbrew switch 2.7.3
pythonbrew venv create proj
Worked like a champ.
I've taken to creating my virtual environments in a .folder underneath my git repo so that I can dispose of the virtual environment without messing with my code and rebuild it if I so desire. I bumped into this technique while working with jenkins which does the git clone for you, then you have to figure out how to build a virtual environment around it.
Python/proj
.proj <---- Virtual environment is in here!
lib
site-packages
settings
requirements
apps
I also have a bash function that does workon for me.
function workon() {
if [ -d ~/Python/$1 ]
then
cd ~/Python/$1
if [ -d .$1 ]
then
. .${1}/bin/activate
else
. bin/activate
cd $1
fi
fi
}
This one is overly complicated to deal with old projects where the clone was done inside the virtual environment as well as the new ones where the virtual environment is inside the project.