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 ncoghlan
Recipients Arfrever, eric.araujo, eric.snow, mattheww, ncoghlan, pitrou
Date 2012-06-13.13:49:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1339595357.35.0.359257845134.issue13475@psf.upfronthosting.co.za>
In-reply-to
Content
I was tempted to just add this (perhaps as a -X option) but, on reflection, I'm going to go with "No, not for 3.3".

I want to take a long hard look at the whole sys.path[0] initialisation process when I update PEP 395 to account for namespace packages, and it doesn't make sense to skip ahead with part of the conclusion. (I may even end up splitting that PEP into two pieces)

I'll also look into the embedding API, to see if/how embedding applications can fully control sys.path initialisation.

Python has survived without this feature for the last couple of decades, there's no need to be hasty in adding it now.
History
Date User Action Args
2012-06-13 13:49:17ncoghlansetrecipients: + ncoghlan, pitrou, mattheww, eric.araujo, Arfrever, eric.snow
2012-06-13 13:49:17ncoghlansetmessageid: <1339595357.35.0.359257845134.issue13475@psf.upfronthosting.co.za>
2012-06-13 13:49:16ncoghlanlinkissue13475 messages
2012-06-13 13:49:16ncoghlancreate