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, mlalic, r.david.murray, serhiy.storchaka
Date 2013-06-20.22:37:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371767847.72.0.236889539376.issue18271@psf.upfronthosting.co.za>
In-reply-to
Content
If all you are changing is headers (and you con't change the CTE), then when you use BytesGenerator to re-serialize the message, it is supposed to preserve the existing CTE/payload.  (Whether or not you call get_payload, regardless of arguments, does not matter; get_payload does not modify the Message object...though set_payload does, of course).

If you have a case where the payload is being re-encoded even though you have not changed the content-type or content-transfer-encoding headers or the payload, then that is a bug.

Of course, if you use just Generator (which is what str uses), the output message must be in ASCII, so in that case it does indeed transcode 8bit payloads to base64.
History
Date User Action Args
2013-06-20 22:37:27r.david.murraysetrecipients: + r.david.murray, barry, serhiy.storchaka, mlalic
2013-06-20 22:37:27r.david.murraysetmessageid: <1371767847.72.0.236889539376.issue18271@psf.upfronthosting.co.za>
2013-06-20 22:37:27r.david.murraylinkissue18271 messages
2013-06-20 22:37:27r.david.murraycreate