RetroSearch Browse

Wed Aug 5 20:35:02 CEST 2009 · https://mail.python.org/pipermail/python-dev/2009-August/091026.html

>>    These files are in 8859-1 encoding (names in comments, at least):
>> http://svn.python.org/view/python/trunk/Lib/encodings/punycode.py
>> http://svn.python.org/view/python/trunk/Lib/test/test_csv.py
>> http://svn.python.org/view/python/trunk/Tools/i18n/msgfmt.py
>> http://svn.python.org/view/python/trunk/Tools/i18n/pygettext.py
>>    If they are not marked as "text/plain; charset=iso-8859-1" I think it's
>> a bug. Either they should be marked, or converted to ascii or utf-8; the
>> coding pseudocomment (directive) should be changed accordingly.
> 
> It's certainly ok to convert them to utf-8 (and add the marker anyway).

No, it's not. PEP 8 mandates that non-ASCII code in the Python source
code is in Latin-1.

Regards,
Martin

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

Showing content from https://mail.python.org/pipermail/python-dev/2009-August/091026.html below:

[Python-Dev] PEP 385: the charset issue