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 steve.dower
Recipients ncoghlan, steve.dower, twouters, vstinner
Date 2019-05-17.15:45:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1558107956.91.0.0691775236391.issue36945@roundup.psfhosted.org>
In-reply-to
Content
I think this should be opt-in, not opt-out.

Imagine you're an existing application and you want to embed Python. Why would you ever want it to suddenly change your global settings like this?

As a general rule, an embedded Python runtime should deal with all the settings it's been provided and not forcibly change *any* of them (though maybe the embedding application will discover bugs and have to update their entire application to deal with it - or switch to a language that isn't so demanding!).

For this specific case, it seems just as easy to opt-in by calling setlocale(LC_CTYPE, "") before initializing Python. We can recommend this in docs and do it ourselves in Py_Main, but I don't see why we'd add a specific option for configuring the user's C runtime.
History
Date User Action Args
2019-05-17 15:45:56steve.dowersetrecipients: + steve.dower, twouters, ncoghlan, vstinner
2019-05-17 15:45:56steve.dowersetmessageid: <1558107956.91.0.0691775236391.issue36945@roundup.psfhosted.org>
2019-05-17 15:45:56steve.dowerlinkissue36945 messages
2019-05-17 15:45:56steve.dowercreate