Eversince upgrading and installing virtualenvwrapper which now has support for all bash shells, I get the following error when the terminal is invoked:


virtualenvwrapper.sh: Could not find Python module virtualenvwrapper.hook_loader using VIRTUALENVWRAPPER_PYTHON=/usr/bin/python. Is the PATH set properly?

I have not seen this error in the older virtualenvwrappers, and I am wondering if it has anything to do with the way python is packaged in Ubuntu? or something else?

Doug writes about extending wrappers, BUT ...But...but, I have not defined a source hook for it and nor am I extending it. Its vanilla, invoked with "mkvirtualenv projectname", "workon" or should that change too? Yeah, Virtualenvwrapper works but I dont like seeing this error message each time the shell is invoked. Its annoying.

UPDATE:

Doug left a comment and I had mailed him that by cloning his repo, I was "doing it wrong". And, what went wrong? This:
0. Cloning doug's repo with hg clone http://bitbucket.org/dhellmann/virtualenvwrapper --which downloaded it to the users home directory. Ex. /home/me.
1. Downloading http://www.doughellmann.com/projects/virtualenvwrapper/ -- it puts the tar.gz file in the directory that one specified in the Firefox settings.

The correct method:

$ sudo easy_install pip

$ sudo pip install virtualenvwrapper which installed a copy of the script in /usr/local/bin and the support libraries are placed in /usr/local/lib/python2.6/dist-packages.

There is a command reference too and during my search I found a wontfix bug which explains why users will have to set a path themselves.