[issue5819] Add PYTHONPREFIXES environment variable

Andrew Svetlov added the comment: Close issue as superseded by venv package. -- resolution: -> out of date stage: -> committed/rejected status: open -> closed ___ Python tracker ___

[issue5819] Add PYTHONPREFIXES environment variable

Christopher Dunn added the comment: I agree. venv solves this problem and more. -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue5819] Add PYTHONPREFIXES environment variable

Andrew Svetlov added the comment: As PEP 405 has been implemented in Python 3.3 this issue can be closed I think. -- nosy: +asvetlov ___ Python tracker ___ __

[issue5819] Add PYTHONPREFIXES environment variable

Éric Araujo added the comment: See also #1298835 and PEP 405. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue5819] Add PYTHONPREFIXES environment variable

Barry A. Warsaw added the comment: I'll look at this in more detail, but I can at least answer one question right now: "The bona-fide known bug: the Debian package mantainer for Python decided to change "site-packages" to "dist-packages" in 2.6, for reasons I still don't quite understand."

[issue5819] Add PYTHONPREFIXES environment variable

Changes by Éric Araujo : -- nosy: +barry, eric.araujo versions: +Python 3.2 -Python 3.1 ___ Python tracker ___ ___ Python-bugs-list mai

[issue5819] Add PYTHONPREFIXES environment variable

Christopher Dunn added the comment: I am not sure that this guy's idea is good, but I think that he deserves more attention. In comments elsewhere on the web, I noticed that people thought the PYTHONUSERBASE site-packages directory could contain .pth files which would serve the same purpose as

[issue5819] Add PYTHONPREFIXES environment variable

Larry Hastings added the comment: Thanks for your battle-tested feedback, Mr. Bicking! I reply inline. > The biggest problem is that the environmental variable is inherited by > subprocesses. [...] Another problem is that scripts aren't really > sticky with respect to the environment. [...]

[issue5819] Add PYTHONPREFIXES environment variable

Ian Bicking added the comment: Also with respect to the patch, for consistency there needs to be changes to distutils to make use of this variable. PYTHONUSERBASE included changes so that you can install based on that variable. -- ___ Python tracke

[issue5819] Add PYTHONPREFIXES environment variable

Ian Bicking added the comment: This has a similar purpose to virtualenv, but using an environmental variable. An earlier package, workingenv, also used an environmental variable, and this led to a set of problems. The biggest problem is that the environmental variable is inherited by subproces

[issue5819] Add PYTHONPREFIXES environment variable

Larry Hastings added the comment: Whoops, didn't classify the patch before submission. -- components: +Library (Lib) type: -> feature request versions: +Python 3.1 ___ Python tracker __

[issue5819] Add PYTHONPREFIXES environment variable

New submission from Larry Hastings : The attached patch adds support for a new environment variable, PYTHONPREFIXES. PYTHONPREFIXES is similar to PYTHONUSERBASE: it lets you add "prefix directories" to be culled for site packages. It differs from PYTHONUSERBASE in three ways: * PYTHONPREFIXES