A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2017-June/148322.html below:

[Python-Dev] PEP 538 (review round 2): Coercing the legacy C locale to a UTF-8 based locale

[Python-Dev] PEP 538 (review round 2): Coercing the legacy C locale to a UTF-8 based locale [Python-Dev] PEP 538 (review round 2): Coercing the legacy C locale to a UTF-8 based localeINADA Naoki songofacandy at gmail.com
Mon Jun 12 04:46:57 EDT 2017
> On 12/06/2017, Nick Coghlan <ncoghlan at gmail.com> wrote:
>>
>> `PYTHONIOENCODING=:strict` remains 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,
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4