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 akuchling, giampaolo.rodola, holdenweb, lregebro, pitrou, r.david.murray, rhettinger
Date 2011-01-13.00:13:43
SpamBayes Score 1.0818964e-08
Marked as misclassified No
Message-id <1294877625.23.0.159415781765.issue9124@psf.upfronthosting.co.za>
In-reply-to
Content
I've been intending to take a look at this issue at some point, but am not sure when I'd get to it.

I took a quick look. It does seems to me that it is true that for data-validity purposes the message files need to be opened in binary and fed to the email package in binary.  But this is so that the message will get decoded using the correct character sets, not to avoid the decoding.  In Python3 it makes no sense to manipulate the subjects as binary strings, so the example of "looping through the messages and printing the subjects" is still going to require decoding.

There may still be ways to make it more efficient for common use cases, but that will require more detailed analysis.
History
Date User Action Args
2011-01-13 00:13:45r.david.murraysetrecipients: + r.david.murray, akuchling, rhettinger, holdenweb, pitrou, giampaolo.rodola, lregebro
2011-01-13 00:13:45r.david.murraysetmessageid: <1294877625.23.0.159415781765.issue9124@psf.upfronthosting.co.za>
2011-01-13 00:13:43r.david.murraylinkissue9124 messages
2011-01-13 00:13:43r.david.murraycreate