[Python-Dev] PEP 538 (review round 2): Coercing the legacy C locale to a UTF-8 based locale (original) (raw)
INADA Naoki songofacandy at gmail.com
Mon Jun 12 04:46:57 EDT 2017
- Previous message (by thread): [Python-Dev] PEP 538 (review round 2): Coercing the legacy C locale to a UTF-8 based locale
- Next message (by thread): [Python-Dev] PEP 538 (review round 2): Coercing the legacy C locale to a UTF-8 based locale
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12/06/2017, Nick Coghlan <ncoghlan at gmail.com> wrote:
PYTHONIOENCODING=:strictremains the preferred way of forcing strict encoding checks on the standard streams, regardless of locale. Then the user of my script has to care that it's written in Python and set that specifically in their crontab or so on...
That's why I think https://bugs.python.org/issue15216 should be fixed in Python 3.7 too.
Python should have one preferable way to specify encoding and error handler from inside of the program, not from envvar or command line argument.
Regards,
- Previous message (by thread): [Python-Dev] PEP 538 (review round 2): Coercing the legacy C locale to a UTF-8 based locale
- Next message (by thread): [Python-Dev] PEP 538 (review round 2): Coercing the legacy C locale to a UTF-8 based locale
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]