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 lemburg
Recipients barry, bgamari, eric.araujo, l0nwlf, lemburg, maxua, r.david.murray, tony_nelson
Date 2010-06-04.09:14:50
SpamBayes Score 0.013068603
Marked as misclassified No
Message-id <4C08C408.8090100@egenix.com>
In-reply-to <1275582683.23.0.384513249134.issue4487@psf.upfronthosting.co.za>
Content
R. David Murray wrote:
> 
> R. David Murray <rdmurray@bitdance.com> added the comment:
> 
> For various reasons the email module has a table of character sets.  What might be most effective would be for the email module to look a character set name up in the codecs module and find out the cannonical name of the character set, and then look that up in its table (ie: remove the aliases table from email completely, and instead depend on codecs to resolve the cannonical name).  Unfortunately the codecs module does not recognize all of the aliases used by email, nor is there necessarily any guarantee that the two modules will agree on the proper cannonical name.

I think that the encodings package should be the only source of
valid aliases and encoding names - after all, you wouldn't be
able to process email content using names or aliases not
appearing in the encodings package tables.

If there are aliases missing, then we can add them there.

If the email packages needs different canonical names, it can apply
its own map on the canonical names returned by the encodings package.
History
Date User Action Args
2010-06-04 09:14:53lemburgsetrecipients: + lemburg, barry, tony_nelson, eric.araujo, maxua, r.david.murray, bgamari, l0nwlf
2010-06-04 09:14:51lemburglinkissue4487 messages
2010-06-04 09:14:50lemburgcreate