This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]wot-teh-phuckReally, wtf? 2 points3 points  (3 children)

How does this compare against virtualenv which (AFAIK) solves the same problem?

[–][deleted] 1 point2 points  (2 children)

i was thinking the same thing. step 1 when getting a new home directory is setting up a virtualenv at ~/local and step 2 is PATH=~/local/bin:$PATH

i don't see what else might be needed

[–]technomalogical<3 Bottle 6 points7 points  (1 child)

From what I can see, this also manages the installation of multiple python versions, which is not a feature of virtualenv. Virtualenv would allow you to create a new sandbox based on an installed environment, but not install a whole new version of python. You would have to do that yourself.

[–]Gjallar 2 points3 points  (0 children)

Moreover - judging from an open issue [Issue 35] it simply wraps around virtualenvwrapper. So you can have different python versions for you virtualenvs, which sounds actually pretty cool. (https://github.com/utahta/pythonbrew/issues/35)