This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mehaase
Recipients alexjc, dstufft, gilgamezh, gracinet, mathieui, mehaase, vinay.sajip, vstinner
Date 2016-07-25.17:40:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Please ignore my previous message and patch. Although it installs a pip script into the virtual environment, the script's shebang points to the global python and not the venv python. I'm trying to figure out why this is, but the pip voodoo is way deeper than I understand. I can only guess that it has to do with sys.executable which appears to point to the normalized path, i.e. the system python instead of the symlink inside the venv.

So I tried dstufft's other suggestion: disable system site packages before bootstrapping pip and then re-enable it afterward. This actually does work in an end-to-end test on my system. So I'm attaching another patch that applies to python 3.5 (1b279c2 on github -- I don't know the equivalent mercurial hash) that is smaller than the previous patch. I don't know what the side effects are of monkeying around with system site packages like this, so apologies in advance if this is a stupid thing to do...
Date User Action Args
2016-07-25 17:40:11mehaasesetrecipients: + mehaase, vinay.sajip, vstinner, mathieui, dstufft, gilgamezh, gracinet, alexjc
2016-07-25 17:40:10mehaasesetmessageid: <>
2016-07-25 17:40:10mehaaselinkissue24875 messages
2016-07-25 17:40:10mehaasecreate