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 eric.araujo, eric.snow, ncoghlan
Date 2011-11-26.05:19:46
SpamBayes Score 5.7969615e-08
Marked as misclassified No
Message-id <1322284787.62.0.250278700261.issue13475@psf.upfronthosting.co.za>
In-reply-to
Content
Yeah, sorry Eric (Snow), you're trying to bite off *way* more than is reasonable by proposing to removing sys.path[0] auto-initialisation. While it has its problems, it's also far too entrenched in people's expections of Python's behaviour to consider removing at this late date. The earliest such a radical change could likely be considered is Python 4.

Éric (Araujo): the "just do the right thing" aspect is covered by PEP 395. This is an orthogonal proposal that allows power users the ability to override the automatic initialisation to handle those cases where it goes wrong.

That said, I may still make this suggestion part of PEP 395 rather than a distinct proposal, even though there's no direct dependency (in either direction) between this suggestion and the other ideas in that PEP.
History
Date User Action Args
2011-11-26 05:19:47ncoghlansetrecipients: + ncoghlan, eric.araujo, eric.snow
2011-11-26 05:19:47ncoghlansetmessageid: <1322284787.62.0.250278700261.issue13475@psf.upfronthosting.co.za>
2011-11-26 05:19:47ncoghlanlinkissue13475 messages
2011-11-26 05:19:46ncoghlancreate