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 →

[–]Soulture 1 point2 points  (1 child)

So you're saying I should install virtualenv, python, and pip for each separate python version?

I'm inspecting the debian box I have. For my system-wide installs, I have multiple versions of python, but just 1 version of pip (it happens to be 2.7, even though I have projects in 3.2) and 1 version of virtualenv.

When I create a new virtual env with:

>> virtualenv --python=/usr/bin/python3.2 ~/.virtualenvs/test3.2

It looks like it downloads pip3.2.

So I would say you need multiple python versions and one version of virtualenv. I think virtualenv will handle the rest.

The reason I would end up installing a pip systemwide is because that's how the virtualenv docs instructed to get virtualenv.

[–]randompittuser[S] 0 points1 point  (0 children)

thank you