Barry A. Warsaw <ba...@python.org> added the comment:
Certainly at a minimum, the docs should describe the exception and workaround
instead of just:
"setlocale() is not thread safe on most systems. Applications typically start
with a call of
import locale
locale.setlocale(locale.LC_ALL, '')
This sets the locale for all categories to the user’s default setting
(typically specified in the LANG environment variable). If the locale is not
changed thereafter, using multithreading should not cause problems."
+0 for a new function in Python 3.2.
For Python 2.7 though, we can't really add that new function or change the
behavior of setlocale() so I'm not sure what the right thing to do is. A
documentation change is probably as good as it's going to get for Python 2.
----------
nosy: +barry
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue1703592>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
