Author r.david.murray
Recipients anadelonbrin, barry, dato, meatballhat, pitrou, r.david.murray, tercero12, vstinner
Date 2010-10-08.11:56:33
SpamBayes Score 1.35659e-06
Marked as misclassified No
Message-id <1286538996.84.0.297813481725.issue4661@psf.upfronthosting.co.za>
In-reply-to
Content
Generator converts 8bit bodies into 7bit bodies by applying an appropriate 7bit CTE.  The reason it does this is that the output of Generator will often be passed to some other Python library function (most often smtplib) that can only handle ASCII unicode input.  That is, Generator now produces a 7bit clean message that can be put on the wire by encoding it to ascii.  This means that RFC-compliant bytes input can be successfully transmitted onward using Generator and smtplib, whereas if Generator produced non-ASCII unicode it would not be possible to pass a message with an 8bit CTE on to smtplib.

The statement about string input and output is a description of email *5.0*, the existing email package in 3.0 and 3.1, before my patch.  The differences between 4.0 and 5.0 were never previously added to the docs, so I had to add them in order to then describe the differences between 5.0 and 5.1.
History
Date User Action Args
2010-10-08 11:56:37r.david.murraysetrecipients: + r.david.murray, barry, anadelonbrin, pitrou, vstinner, dato, tercero12, meatballhat
2010-10-08 11:56:36r.david.murraysetmessageid: <1286538996.84.0.297813481725.issue4661@psf.upfronthosting.co.za>
2010-10-08 11:56:34r.david.murraylinkissue4661 messages
2010-10-08 11:56:33r.david.murraycreate