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 ncoghlan, vstinner
Date 2017-07-05.05:48:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1499233701.11.0.976098235682.issue30836@psf.upfronthosting.co.za>
In-reply-to
Content
Note that as far as I'm aware, AIX doesn't actually provide any of our coercion target locales yet, so the question in my previous comment is about how we want 3.7.x releases to behave on AIX if IBM *do* introduce a C.UTF-8 locale.

The main argument I see in favour of leaving locale coercion enabled is that the latin-1 default will cope with UTF-8 encoded data from Python 3.7+ applications (even if it displays them incorrectly), but may raise UnicodeEncodeError if an application attempts to create arbitrary Unicode filenames, or write arbitrary unicode data to the standard streams.
History
Date User Action Args
2017-07-05 05:48:21ncoghlansetrecipients: + ncoghlan, vstinner
2017-07-05 05:48:21ncoghlansetmessageid: <1499233701.11.0.976098235682.issue30836@psf.upfronthosting.co.za>
2017-07-05 05:48:21ncoghlanlinkissue30836 messages
2017-07-05 05:48:20ncoghlancreate