Message105121
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:30 | r.david.murray | set | recipients:
+ r.david.murray, barry, ynkdir, l0nwlf |
2010-05-06 01:54:30 | r.david.murray | set | messageid: <1273110870.37.0.304494287329.issue7472@psf.upfronthosting.co.za> |
2010-05-06 01:54:28 | r.david.murray | link | issue7472 messages |
2010-05-06 01:54:27 | r.david.murray | create | |
|