Message162708
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. |
|
Date |
User |
Action |
Args |
2012-06-13 13:49:17 | ncoghlan | set | recipients:
+ ncoghlan, pitrou, mattheww, eric.araujo, Arfrever, eric.snow |
2012-06-13 13:49:17 | ncoghlan | set | messageid: <1339595357.35.0.359257845134.issue13475@psf.upfronthosting.co.za> |
2012-06-13 13:49:16 | ncoghlan | link | issue13475 messages |
2012-06-13 13:49:16 | ncoghlan | create | |
|