Marc-Andre Lemburg <m...@egenix.com> added the comment: R. David Murray wrote: > > R. David Murray <rdmur...@bitdance.com> added the comment: > > euc_jp and euc_kr seem to be backward (that is, codecs translates them to the > _ version, instead of translating the _ version to the - version). I worry > that there might be other deviations from the standard email names. I would > suggest we pull the list of preferred MIME names from the IANA charset > registry and make a test out of them in the email package. If changing the > name returned by codecs is determined to not be acceptable, then those > entries will need to remain in the charset module ALIASES table and the > codecs-check logic adjusted accordingly. > > Unfortunately the IANA registry does not list MIME names for all of the > charsets in common use, and the canonical names are not always the ones > commonly used in email. Hopefully the codecs registry is using the most > common name for those, and hopefully if there are differences it won't break > any user code, since any reasonable email code should be coping with the > aliases in any case.
The way I understand the patch was that the email package will start to use the encoding aliases for determining the codec name instead of its own list. That is: only for decoding the input data, not for creating a correct MIME encoding name in output data. ---------- title: The email package should defer to the codecs module for all aliases -> The email package should defer to the codecs module for all aliases _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8898> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
