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, abarry, ezio.melotti, lemburg, methane, ncoghlan, r.david.murray, vstinner, yan12125
Date 2016-12-17.07:56:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1481961380.58.0.954586765946.issue28180@psf.upfronthosting.co.za>
In-reply-to
Content
Making an explicit note of this so I remember to mention it in the draft PEP: one of the biggest problems that arises in any attempt at a Python-only solution to overriding the locale is that we can end up disagreeing with C/C++ extensions, and this is *especially* a problem when sharing a process with GUI frameworks like Tcl/Tk, Qt, and GTK (since they tend to read the process-wide settings, rather than querying anything that CPython configures during normal operation).

So the approach I'm proposing is to implement a C->C.UTF-8 locale override in the *actual python CLI executable*, and then in the dynamically linked library we only emit a warning if we detect the C locale, we don't actually do anything to change it.
History
Date User Action Args
2016-12-17 07:56:20ncoghlansetrecipients: + ncoghlan, lemburg, vstinner, ezio.melotti, r.david.murray, methane, yan12125, abarry, Jan Niklas Hasse
2016-12-17 07:56:20ncoghlansetmessageid: <1481961380.58.0.954586765946.issue28180@psf.upfronthosting.co.za>
2016-12-17 07:56:20ncoghlanlinkissue28180 messages
2016-12-17 07:56:19ncoghlancreate