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 r.david.murray
Recipients eric.araujo, ezio.melotti, l0nwlf, lemburg, maker, r.david.murray
Date 2011-05-26.19:21:29
SpamBayes Score 0.0013650942
Marked as misclassified No
Message-id <1306437690.58.0.560040074084.issue8898@psf.upfronthosting.co.za>
In-reply-to
Content
Well, my thought was to avoid having multiple charset alias lists in the stdlib, and reusing the one in codecs, which is larger than the one in email, seemed to make sense.  This came up because a bug was reported where email (silently) failed to encode a string because the charset alias, while present in codecs, wasn't present in the email ALIASES table.

I suppose that as an alternative I could add full support for the IANA aliases list to email.  Email is the most likely place to run in to variant charset aliases anyway.

If that's the way we go, then this issue should be changed over to covering just updating codecs with the missing aliases, and a new issue opened for adding full IANA alias support to email.
History
Date User Action Args
2011-05-26 19:21:30r.david.murraysetrecipients: + r.david.murray, lemburg, ezio.melotti, eric.araujo, l0nwlf, maker
2011-05-26 19:21:30r.david.murraysetmessageid: <1306437690.58.0.560040074084.issue8898@psf.upfronthosting.co.za>
2011-05-26 19:21:30r.david.murraylinkissue8898 messages
2011-05-26 19:21:29r.david.murraycreate