Author kristjan.jonsson
Recipients Arfrever, eric.araujo, eric.snow, gregory.p.smith, kristjan.jonsson, mattheww, ncoghlan, pitrou
Date 2012-11-23.09:52:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353664359.4.0.420204082777.issue13475@psf.upfronthosting.co.za>
In-reply-to
Content
Butting in here:
Early on in the startup, a search is made for "site.py" using automatic sys.path settings.  Do the suggestions here propose to override this?  I know there is a -s flag, but all these flags start to be confusing.

I have been looking for ways to completely ignore automatic settings for sys.path, either from internal heuristics (either build environment or installed environment) or PYTHONPATH.
The reason for this is that as a developer in a large project, one that has many branches, each with their potentially different version of python compiled and with their own libraries, and where a "standard" python distribution may even be installed on the machine as well, we still want to be able to run scripts with each branch' own python with relative simplicity with some sort of guarantee that we are not inadvertently pulling in modules from other, unrelated branches, or god forbid, the "installed" python.

PEP 405 seemed to go a long way, although it didn't provide a means in the pyvenv.cfg to completely override sys.path from the startup.

I wonder if there isn't a synergy here with PEP 405, e.g. would it make sense to have a pyvenv.cfg file next to the __main__.py file?
History
Date User Action Args
2012-11-23 09:52:39kristjan.jonssonsetrecipients: + kristjan.jonsson, gregory.p.smith, ncoghlan, pitrou, mattheww, eric.araujo, Arfrever, eric.snow
2012-11-23 09:52:39kristjan.jonssonsetmessageid: <1353664359.4.0.420204082777.issue13475@psf.upfronthosting.co.za>
2012-11-23 09:52:39kristjan.jonssonlinkissue13475 messages
2012-11-23 09:52:38kristjan.jonssoncreate