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 georg.brandl
Recipients ezio.melotti, georg.brandl, lemburg
Date 2009-05-02.09:20:22
SpamBayes Score 3.2168712e-13
Marked as misclassified No
Message-id <1241256026.69.0.184003855831.issue5902@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think this is a good idea.  Accepting all common forms for
encoding names means that you can usually give Python an encoding name
from, e.g. a HTML page, or any other file or system that specifies an
encoding.  If we only supported, e.g., "UTF-8" and no other spelling,
that would make life much more difficult.  If you look into
encodings/__init__.py, you can see that throwing out all
non-alphanumerics is a conscious design choice in encoding name
normalization.

The only thing I don't know is why "utf" is an alias for utf-8.

Assigning to Marc-Andre, who implemented most of codecs.
History
Date User Action Args
2009-05-02 09:20:26georg.brandlsetrecipients: + georg.brandl, lemburg, ezio.melotti
2009-05-02 09:20:26georg.brandlsetmessageid: <1241256026.69.0.184003855831.issue5902@psf.upfronthosting.co.za>
2009-05-02 09:20:25georg.brandllinkissue5902 messages
2009-05-02 09:20:23georg.brandlcreate