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 belopolsky, eric.araujo, ezio.melotti, jcea, lemburg, pitrou, rhettinger, sdaoden, vstinner
Date 2011-02-26.12:55:22
SpamBayes Score 2.8547165e-11
Marked as misclassified No
Message-id <4D68F839.4080603@egenix.com>
In-reply-to <1298683573.26.0.881371064369.issue11303@psf.upfronthosting.co.za>
Content
Raymond Hettinger wrote:
> 
> Raymond Hettinger <rhettinger@users.sourceforge.net> added the comment:
> 
>> If you agree, Raymond, I'll backport the patch.
> 
> Yes.  That will address Antoine's legitimate concern about making other backports harder, and it will get all the Python's to use the canonical spelling.

Ok, I'll backport both the normalization and Alexander's patch.

> For other spellings like "utf8" or "latin1", I wonder if it would be useful to emit a warning/suggestion to use the standard spelling.

While it would make sense for Python programs, it would not for
cases where the encoding is read from some other source, e.g.
an XML encoding declaration.

However, perhaps we could have a warning which is disabled
per default and can be enabled using the -W option.
History
Date User Action Args
2011-02-26 12:55:23lemburgsetrecipients: + lemburg, rhettinger, jcea, belopolsky, pitrou, vstinner, ezio.melotti, eric.araujo, sdaoden
2011-02-26 12:55:22lemburglinkissue11303 messages
2011-02-26 12:55:22lemburgcreate