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 Chris.Waigl, ajaksu2, alexz, barry, bgamari, catlee, checat, eric.araujo, forest_atq, fsteinel, gotgenes, guettli, jnoller, orsenthil, pitrou, r.david.murray, shazow, tamentis
Date 2011-02-15.21:55:42
SpamBayes Score 2.3123206e-07
Marked as misclassified No
Message-id <>
In principle I think something like this should go in.  Since it is a Message subclass, I'd like it to follow the current Message API whether or not it is located in the email package.  __str__ and as_string have the right default for line length (no folding).  The current default for line endings is \n, and I think the class should stick with that.  You can't use __str__ or as_string to generate what you send on the wire if you are supporting binary data.

I am planning additions to the email API that will make integrating this class and adjusting the generated line endings easier.  For the latter (assuming the email-sig approves) I plan a __bytes__ method that will generate "wire format", which would include using \r\n line endings and should be just what you need.

The current email package does not support the binary content transfer encoding, only 8bit.  Support for the binary CTE is another planned addition for 3.3, and I think it can be prioritized ahead of most other features, given that this code needs it.

So, you might want to wait until the email pieces are in place, and possibly even help me develop them :)
Date User Action Args
2011-02-15 21:55:44r.david.murraysetrecipients: + r.david.murray, barry, guettli, orsenthil, pitrou, catlee, gotgenes, ajaksu2, jnoller, eric.araujo, forest_atq, fsteinel, shazow, bgamari, alexz, tamentis, checat, Chris.Waigl
2011-02-15 21:55:44r.david.murraysetmessageid: <>
2011-02-15 21:55:43r.david.murraylinkissue3244 messages
2011-02-15 21:55:42r.david.murraycreate