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 docs@python, ncoghlan, ned.deily, vstinner, zezollo
Date 2018-06-24.03:29:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1529810946.57.0.56676864532.issue33934@psf.upfronthosting.co.za>
In-reply-to
Content
This statement is no longer correct: "when python starts, it runs using the C locale, on any platform (Windows, Linux, BSD), any python version (2, 3...), until locale.setlocale() is used to set another locale."

The Python 3 text model doesn't work properly in the legacy C locale due to the assumption of ASCII as the preferred text encoding, so we run setlocale(LC_ALL, "") early in the startup sequence in order to switch to something more sensible. In Python 3.7+, we're even more opinionated about that, and explicitly coerce the C locale to a UTF-8 based one if there's one available.

If our docs are still saying otherwise anywhere, then our docs are outdated, and need to be fixed.
History
Date User Action Args
2018-06-24 03:29:06ncoghlansetrecipients: + ncoghlan, vstinner, ned.deily, docs@python, zezollo
2018-06-24 03:29:06ncoghlansetmessageid: <1529810946.57.0.56676864532.issue33934@psf.upfronthosting.co.za>
2018-06-24 03:29:06ncoghlanlinkissue33934 messages
2018-06-24 03:29:05ncoghlancreate