RetroSearch Browse

Wed Aug 5 17:08:25 CEST 2009 · https://mail.python.org/pipermail/python-dev/2009-August/091017.html

Oleg Broytmann <phd <at> phd.pp.ru> writes:
> 
>    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).
There's no point in having different charsets used throughout the code base,
except for testing purposes (just as there's no point in having different
indentation rules used for the same file type throughout the code base ;-)).

Regards

Antoine.

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

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

[Python-Dev] PEP 385: the charset issue