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 Jan Niklas Hasse, Sworddragon, abarry, akira, barry, ezio.melotti, lemburg, methane, ncoghlan, r.david.murray, vstinner, yan12125
Date 2017-01-05.10:54:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1483613688.04.0.668880312544.issue28180@psf.upfronthosting.co.za>
In-reply-to
Content
The PEP already explains how other runtimes achieve UTF-8 and UTF-18-LE everywhere: by ignoring the C/C++ locale entirely. While this breaks integration with other C/C++ components, the developers of those languages and runtimes simply don't care, as they never supported integrating with those components in the first place.

CPython doesn't have that luxury, since it is used extensively in locale aware desktop applications.
History
Date User Action Args
2017-01-05 10:54:48ncoghlansetrecipients: + ncoghlan, lemburg, barry, vstinner, ezio.melotti, r.david.murray, methane, akira, Sworddragon, yan12125, abarry, Jan Niklas Hasse
2017-01-05 10:54:48ncoghlansetmessageid: <1483613688.04.0.668880312544.issue28180@psf.upfronthosting.co.za>
2017-01-05 10:54:48ncoghlanlinkissue28180 messages
2017-01-05 10:54:47ncoghlancreate