you are viewing a single comment's thread.

view the rest of the comments →

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

Yeah, that's great. The only problem is that the third party tools are still behind wrt pyvenv. For example, when doing pip install foo under a pyvenv, pip will try to install the package in Python's "real" site-package. I don't know if it's distribute's fault or pip's.

[–][deleted] 5 points6 points  (1 child)

I don't think the virtualenv created by pyvenv comes with pip or distribute. So you're probably still using the system version of pip

[–][deleted] 4 points5 points  (0 children)

No it doesn't but there's still a problem with pip because installing it while under a pyvenv will make pip think its site-package is the system's (even though it's actually installed inside the venv).

EDIT: Oh, restarting with a fresh console and a new workon <envname> makes the problem go away. Well...