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 lemburg
Recipients eryksun, ezio.melotti, lemburg, methane, vstinner
Date 2022-03-30.09:40:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <89a3f459-ac9e-a4d5-e31c-686eecd0f86d@egenix.com>
In-reply-to <1648625156.52.0.0183797354699.issue47000@roundup.psfhosted.org>
Content
Please see https://bugs.python.org/issue47000#msg415769 for what Victor
suggested.

In particular, the locale module uses the "no underscore" convention.
Not sure whether it's good to start using snake case now, but I'm also
not against it.

I would like to reiterate my concern with the "locale" encoding, though.

As mentioned earlier, I believe it adds too much magic. It would be better
to leave this in the hands of the applications and not try to guess
the correct encoding.

It's better to expose easy to use APIs to access the various different
settings and point users to those rather than try to do a best effort
guess... explicit is better than implicit.

After all, Mojibake potentially corrupts important data, without the
alerting the user and that's not really what we should be after (e.g.
UTF-8 is valid Latin-1 in most cases and this is a real problem we often
run into in Germany with our Umlauts).
History
Date User Action Args
2022-03-30 09:40:35lemburgsetrecipients: + lemburg, vstinner, ezio.melotti, methane, eryksun
2022-03-30 09:40:35lemburglinkissue47000 messages
2022-03-30 09:40:35lemburgcreate