homepage

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 r.david.murray
Recipients Arfrever, lemburg, loewis, pitrou, r.david.murray, sdaoden, vstinner
Date 2011年02月01日.02:43:23
SpamBayes Score 4.0270556e-06
Marked as misclassified No
Message-id <1296528204.06.0.564576662798.issue11022@psf.upfronthosting.co.za>
In-reply-to
Content
Steffan: I'm not sure what your post means, but I think there is a chance you might be confused about something. Python should *never* change the locale from the C locale. A Python *program* can do so, by calling setlocale, but Python itself should not. This is because when an arbitrary Python program is run, it needs to run in the C locale *unless it chooses otherwise*. To do anything else would produce a myriad portability problems for any code that is affected by locale settings (especially when the programmer doesn't know that it is so affected).
This is orthogonal to the issue of deciding what encoding to use for various bits of I/O, where Python may need to discover what locale the user has chosen as a default. It's too bad libc makes this so hard to do safely.
History
Date User Action Args
2011年02月01日 02:43:24r.david.murraysetrecipients: + r.david.murray, lemburg, loewis, pitrou, vstinner, Arfrever, sdaoden
2011年02月01日 02:43:24r.david.murraysetmessageid: <1296528204.06.0.564576662798.issue11022@psf.upfronthosting.co.za>
2011年02月01日 02:43:23r.david.murraylinkissue11022 messages
2011年02月01日 02:43:23r.david.murraycreate

AltStyle によって変換されたページ (->オリジナル) /