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 Marco.Amadori
Recipients Marco.Amadori, asvetlov, carljm, eric.araujo, ned.deily, vinay.sajip
Date 2012-11-18.21:25:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> The question is: is this still necessary? Why exactly does
> "posix_local" need this, and does it need it for Python 3.3, 3.4 etc? 
> Adding Carl to nosy, hoping he can shed some light on this.

I hope to see the light on that too. ;-)

Meanwhile, my problem was that after creating the virtualenv, as cited in the blog post above linked, I got stuck in installing pip (and thus distribute) in that virtualenv, because 'VENV/local/bin' is not in the $PATH (and it seems reasonable for a virtualenv that this will remain stable).

So, (IMHO) if changing the $PATH is not a good idea, either python should do:

1. patch distribute and pip to do not install in ./local by default if in a VENV. (enviroment variable based?, whatever)

2. create the links after creating the VENV (my naïve solution)

Am I right or I completely hit the wrong issue?
Date User Action Args
2012-11-18 21:25:27Marco.Amadorisetrecipients: + Marco.Amadori, vinay.sajip, ned.deily, carljm, eric.araujo, asvetlov
2012-11-18 21:25:27Marco.Amadorisetmessageid: <>
2012-11-18 21:25:27Marco.Amadorilinkissue16480 messages
2012-11-18 21:25:27Marco.Amadoricreate