[issue9548] locale can be imported at startup but relies on too many library modules
Nick Coghlan
report at bugs.python.org
Sat Aug 14 09:49:44 CEST 2010
Nick Coghlan <ncoghlan at gmail.com> added the comment:
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.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9548>
_______________________________________
More information about the Python-bugs-list
mailing list