R. David Murray <rdmur...@bitdance.com> added the comment: 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. ---------- resolution: accepted -> fixed stage: unit test needed -> committed/rejected status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7472> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
