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 vstinner
Recipients Greg Price, benjamin.peterson, ezio.melotti, lemburg, serhiy.storchaka, vstinner
Date 2019-08-14.10:19:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Handling locales correctly is a pain. Each platform uses different locale names (different Linux distributions, Windows, FreeBSD, macOS, etc.). For example, en_US.UTF-8 vs en_US.utf8. For example, there are tons of bugs related to locale.getdefaultlocale() which tries to be smart on parsing locales. I'm fixing locale encoding bugs for 10 years and I'm not done yet: there are still many open bugs.

I suggest you to first create a module on PyPI to experiment getting the locale and attempt to implement Unicode algorithms which depend on the locale.

Maintaining Python is already expensive, I would prefer to not complicate the codebase too much with locales. There are already enough bugs waiting for you to be fixed ;-)
Date User Action Args
2019-08-14 10:19:24vstinnersetrecipients: + vstinner, lemburg, benjamin.peterson, ezio.melotti, serhiy.storchaka, Greg Price
2019-08-14 10:19:24vstinnersetmessageid: <>
2019-08-14 10:19:24vstinnerlinkissue37848 messages
2019-08-14 10:19:23vstinnercreate