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 barry, l0nwlf, r.david.murray, ynkdir
Date 2010-05-06.01:54:27
SpamBayes Score 2.1068088e-05
Marked as misclassified No
Message-id <>
It turns out that email5 (py3k), because it is using unicode for the payload, doesn't do the encoding to the output character set until later in the process.  Specifically, charset.body_encode no longer does the input-to-output charset conversion.  The if test in the exception clause in encoders.encode_7or8bit really is needed in email5.  So in r80855 I just port the test to py3k.  Typo fix and test also merged to 3.1 in r80856.

Hopefully that's the last we need to do on this issue.
Date User Action Args
2010-05-06 01:54:30r.david.murraysetrecipients: + r.david.murray, barry, ynkdir, l0nwlf
2010-05-06 01:54:30r.david.murraysetmessageid: <>
2010-05-06 01:54:28r.david.murraylinkissue7472 messages
2010-05-06 01:54:27r.david.murraycreate