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, beazley, georg.brandl, r.david.murray
Date 2010-01-07.19:27:46
SpamBayes Score 0.002570132
Marked as misclassified No
Message-id <1262892468.8.0.13386368842.issue4766@psf.upfronthosting.co.za>
In-reply-to
Content
We've concluded that the email package does need to be able to read bytes.  To do this and still support reading text, we're going to have to change the API.  So the docs will get fixed when they get rewritten for the new API.

Patches to the 3.1 docs to clarify the current situation would probably be accepted and applied, but I suspect the email team is not going to provide them due to lack of time :(.
History
Date User Action Args
2010-01-07 19:27:48r.david.murraysetrecipients: + r.david.murray, barry, georg.brandl, beazley
2010-01-07 19:27:48r.david.murraysetmessageid: <1262892468.8.0.13386368842.issue4766@psf.upfronthosting.co.za>
2010-01-07 19:27:47r.david.murraylinkissue4766 messages
2010-01-07 19:27:46r.david.murraycreate