I wonder why pythonbrew gets no love - http://stacktoheap.com/blog/2013/03/11/why-use-virtualenv-wh...
For me, pythonbrew + autoenv ( https://github.com/kennethreitz/autoenv ) is must for development.
For me, pythonbrew + autoenv ( https://github.com/kennethreitz/autoenv ) is must for development.
If you are from ruby / rails world, you will love and be at home with pythonbrew.
Because of that, I've gone back to using homebrew to compile multiple versions of python and letting tox utilize those. Homebrew takes care of pip & distribute so adding virtualenv & virtualenvwrapper is a simple oneliner after the fact.
So I can just do workon myproject and be instantly transported to the right place with the right environment.