[issue4766] email documentation needs to be precise about strings/bytes

R. David Murray added the comment: The wording was clarified for 3.2 as part of the fix for issue 4661. This does not help the 3.1 docs, so if someone wants to suggest a patch for the 3.1 docs we can reopen the issue. -- resolution: postponed -> fixed stage: -> committed/rejected st

[issue4766] email documentation needs to be precise about strings/bytes

Changes by Barry A. Warsaw : -- assignee: barry -> r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue4766] email documentation needs to be precise about strings/bytes

R. David Murray added the comment: 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 clar

[issue4766] email documentation needs to be precise about strings/bytes

Changes by Georg Brandl : -- assignee: georg.brandl -> barry nosy: +barry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsu

[issue4766] email documentation needs to be precise about strings/bytes

New submission from David M. Beazley : Documentation for the email package needs to be more clear about the usage of strings and bytes. In particular: 1. All operations that parse email messages such as message_from_file() or message_from_string() operate on *text*, not binary data. So,