➜

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-10-12.07:59:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1413100745.93.0.11060526665.issue22490@psf.upfronthosting.co.za>
In-reply-to
Content 
> Ronald's change ... changed the stub launcher to no longer do a realpath() on the executable name
> which means that sys.executable contains the path to the Python stub launcher whether or not in a venv

Ronald's change doesn't do a realpath() on the executable name itself, but it *does* do a realpath() on the executable's directory. This seems to be what's causing the problem in Homebrew builds: there are two levels of symlink at play.

/usr/local/bin/python3.4 -> /usr/local/opt/python3/bin/python3.4 -> /usr/local/Cellar/python3/3.4.1_1/Frameworks/Python.framework/Versions/3.4/bin/python3.4

Because of the realpath(), the "wrong" stub launcher (from Homebrew's perspective) gets pointed to by the environment variable. At least, if my understanding is correct.

https://github.com/pypa/pip/issues/2031#issuecomment-56294599
History
Date User Action Args
2014-10-12 07:59:05vinay.sajipsetrecipients: + vinay.sajip, ronaldoussoren, ned.deily, tdsmith
2014-10-12 07:59:05vinay.sajipsetmessageid: <1413100745.93.0.11060526665.issue22490@psf.upfronthosting.co.za>
2014-10-12 07:59:05vinay.sajiplinkissue22490 messages
2014-10-12 07:59:05vinay.sajipcreate