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-27.14:24:05
SpamBayes Score 0.0084863845
Marked as misclassified No
Message-id <1306506246.69.0.618156765056.issue8898@psf.upfronthosting.co.za>
In-reply-to
Content
Prompted on IRC, I see I missed the file because it was so short.

This still isn't what I'm looking for.  We are assuming that email is going to use the codec eventually so that it is not a bad thing to have charset pre-populate the codec cache.  So what I'm looking for is:

    try:
        python_name = codecs.lookup(input_charset).name
        mime_name = ALIASES.get(python_name, input_charset)
    except LookupError:
        mime_name = input_charset

MAL's idea was to implement the ALIASES step via a two-way mapping in the encodings module (python-canonical-name <=> MIME-preferred-name).  That would be fine, too, but the email.charset logic should look like the above however the table is implemented.
History
Date User Action Args
2011-05-27 14:24:06r.david.murraysetrecipients: + r.david.murray, lemburg, ezio.melotti, eric.araujo, l0nwlf, maker
2011-05-27 14:24:06r.david.murraysetmessageid: <1306506246.69.0.618156765056.issue8898@psf.upfronthosting.co.za>
2011-05-27 14:24:06r.david.murraylinkissue8898 messages
2011-05-27 14:24:05r.david.murraycreate