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 Arfrever, Eric.Hanchrow, apollo13, barry, r.david.murray, vajrasky
Date 2013-10-31.05:38:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1383197933.66.0.731679841681.issue19063@psf.upfronthosting.co.za>
In-reply-to
Content
cte base64 I think (see below).

Basically, set_payload should be putting the surrogateescape encoded utf-8 into the _payload (which it should now be doing), and probably calling set_charset.  The cte will at that point be 8bit, but when as_string calls Generator, it will get converted to 7bit clean by doing (I think) a base64 encode and emitting that as the CTE.  I have to look through the code to remind myself how it all works, which I haven't had time for yet, which is why I haven't tried to make a fix myself yet.

(Yes, this is poor design, but we are dealing with a long line of legacy code and API here...)
History
Date User Action Args
2013-10-31 05:38:53r.david.murraysetrecipients: + r.david.murray, barry, Arfrever, apollo13, vajrasky, Eric.Hanchrow
2013-10-31 05:38:53r.david.murraysetmessageid: <1383197933.66.0.731679841681.issue19063@psf.upfronthosting.co.za>
2013-10-31 05:38:53r.david.murraylinkissue19063 messages
2013-10-31 05:38:53r.david.murraycreate