Marc-Andre Lemburg <m...@egenix.com> added the comment: On 2009-05-02 11:20, Georg Brandl wrote: > Georg Brandl <ge...@python.org> added the comment: > > 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.
-1 on making codec names strict. The reason why we have to many aliases is to enhance compatibility with other software and data, not to encourage use of these aliases in Python itself. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5902> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
