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, python-dev, r.david.murray
Date 2013-03-07.22:57:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362697062.11.0.959168864935.issue14645@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not going to fix this in Python2.  While the problem exists there, it hasn't ever been reported as a bug.  As noted earlier, this is probably primarily due to the fact that it would be very exceptional to read an email in python2 with anything other than universal newline mode, and Python2 provides no way to emit a message with anything other than \n linesep other than smtplib.sendmail, which does the \n to \r\n translation.  In Python3, in contrast, reading a message as binary is common, and we have smtplib.send_message, which writes the message directly using a \r\n linesep instead of doing a post-transformation the way smtplib.sendmail does.
History
Date User Action Args
2013-03-07 22:57:42r.david.murraysetrecipients: + r.david.murray, barry, python-dev
2013-03-07 22:57:42r.david.murraysetmessageid: <1362697062.11.0.959168864935.issue14645@psf.upfronthosting.co.za>
2013-03-07 22:57:42r.david.murraylinkissue14645 messages
2013-03-07 22:57:41r.david.murraycreate