Message86935
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. |
|
Date |
User |
Action |
Args |
2009-05-02 09:20:26 | georg.brandl | set | recipients:
+ georg.brandl, lemburg, ezio.melotti |
2009-05-02 09:20:26 | georg.brandl | set | messageid: <1241256026.69.0.184003855831.issue5902@psf.upfronthosting.co.za> |
2009-05-02 09:20:25 | georg.brandl | link | issue5902 messages |
2009-05-02 09:20:23 | georg.brandl | create | |
|