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 vinay.sajip
Recipients ned.deily, ronaldoussoren, tdsmith, vinay.sajip
Date 2014-11-09.19:39:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I don't quite understand why you use __PYVENV_LAUNCHER__

When I first developed the venv functionality it was definitely needed, but it looks as if it is not needed now. Perhaps to fix this completely, the following needs to be done, on the assumption that __PYVENV_LAUNCHER__ is no longer needed:

1. Remove the reference to it in distlib, and use sys.executable instead. Once pip incorporates this fix, the Homebrew problem should go away. (I have already made the change in the distlib repo, but this needs to be released in order for pip to consider vendoring it, and then pip needs to be released before Python can incorporate it).

2. Remove references to the environment variable in Python itself, using sys.executable instead.

As the env var was an implementation detail, ISTM it could be removed in a 3.4 point release - would you agree?
Date User Action Args
2014-11-09 19:39:53vinay.sajipsetrecipients: + vinay.sajip, ronaldoussoren, ned.deily, tdsmith
2014-11-09 19:39:53vinay.sajipsetmessageid: <>
2014-11-09 19:39:53vinay.sajiplinkissue22490 messages
2014-11-09 19:39:53vinay.sajipcreate