➜

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 belopolsky
Recipients belopolsky, eric.araujo, ezio.melotti, jcea, lemburg, pitrou, rhettinger, sdaoden, vstinner
Date 2011-02-26.01:39:38
SpamBayes Score 1.4877669e-09
Marked as misclassified No
Message-id <AANLkTi=z4oRgU72wtj-yV_M_0nWx5H7GBuPzAuSLdMw4@mail.gmail.com>
In-reply-to <1298683750.59.0.313085841642.issue11303@psf.upfronthosting.co.za>
Content 
On Fri, Feb 25, 2011 at 8:29 PM, Antoine Pitrou <report@bugs.python.org> wrote:
..
>> For other spellings like "utf8" or "latin1", I wonder if it would be
>> useful to emit a warning/suggestion to use the standard spelling.
>
> No, it would be an useless annoyance.

If we ever decide to get rid of codec aliases in the core and require
users to translate names found in various internet standards to
canonical Python spellings, we will have to issue deprecation warnings
before that.

As long as we recommend using say XML encoding metadata as is, we
cannot standardize on Python spellings because they differ from XML
standard.  (For example, Python uses "latin-1" and proper XML only
accepts "latin1". Of course, we can ask everyone to use iso-8859-1
instead, but how many users can remember that name?)
History
Date User Action Args
2011-02-26 01:39:39belopolskysetrecipients: + belopolsky, lemburg, rhettinger, jcea, pitrou, vstinner, ezio.melotti, eric.araujo, sdaoden
2011-02-26 01:39:38belopolskylinkissue11303 messages
2011-02-26 01:39:38belopolskycreate