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 brett.cannon, lemburg, mark.dickinson, ncoghlan, orsenthil, pitrou, rhettinger, vstinner
Date 2010-08-14.07:49:31
SpamBayes Score 4.115619e-11
Marked as misclassified No
Message-id <1281772184.64.0.787021281298.issue9548@psf.upfronthosting.co.za>
In-reply-to
Content
As we move more and more infrastructure into Python code, we're going to see this pattern (i.e. a bootstrap module underlying the real module) more and more often (e.g. I seem to recall Brett has to do something similar when playing with the pure Python __import__ implementation).

I don't have an issue with it - it's a solid, standard solution to a recurring problem with otherwise circular dependencies.

The only changes I would suggest to Antoine's patch are to explicitly scope "interpreter startup" in the _bootlocale docstring (to make it clear that sitecustomize.py should use the ordinary locale module) and to mention the nature of _bootlocale in a comment just before the "from _bootlocale import *" line in locale.py.
History
Date User Action Args
2010-08-14 07:49:44ncoghlansetrecipients: + ncoghlan, lemburg, brett.cannon, rhettinger, mark.dickinson, orsenthil, pitrou, vstinner
2010-08-14 07:49:44ncoghlansetmessageid: <1281772184.64.0.787021281298.issue9548@psf.upfronthosting.co.za>
2010-08-14 07:49:32ncoghlanlinkissue9548 messages
2010-08-14 07:49:31ncoghlancreate