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 ezio.melotti, koobs, ncoghlan, ned.deily, ronaldoussoren, vstinner
Date 2017-12-07.00:28:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1512606515.62.0.213398074469.issue32238@psf.upfronthosting.co.za>
In-reply-to
Content
Right now, the legacy locale detection introduced in PEP 538 doesn't trigger for "LANG=POSIX" and "LC_CTYPE=POSIX" on macOS and other *BSD systems.

This is because we're looking specifically for "C" as the response from "setlocale(LC_CTYPE, NULL)", which works on Linux (where glibc reports "C" if you configured "POSIX"), but not on *BSD systems (where POSIX and C behave the same way, but are still reported as distinct locales).

As per Jakub Wilk's comments at https://mail.python.org/pipermail/python-dev/2017-December/151105.html, this isn't right: we should allow either string to be returned from setlocale, and consider both of them as indicating a legacy locale to be coerced to an explicitly UTF-8 based one if possible.
History
Date User Action Args
2017-12-07 00:28:35ncoghlansetrecipients: + ncoghlan, ronaldoussoren, vstinner, ned.deily, ezio.melotti, koobs
2017-12-07 00:28:35ncoghlansetmessageid: <1512606515.62.0.213398074469.issue32238@psf.upfronthosting.co.za>
2017-12-07 00:28:35ncoghlanlinkissue32238 messages
2017-12-07 00:28:35ncoghlancreate