➜

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 Alexander.Kruppa, barry, jayvdb, python-dev, r.david.murray, xZise, 天一.何
Date 2016-09-11.21:27:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1473629242.04.0.679911071211.issue19003@psf.upfronthosting.co.za>
In-reply-to
Content 
I've fixed this to the extent that it is possible without adding support for the 'binary' CTE.  That is, \r, \n, and \r\n are still replaced with the 'correct' line ending characters, which is the correct behavior under the RFCs even for binary data if the CTE is not 'binary'.  Issue 18886 covers the enhancement of supporting the binary CTE.
History
Date User Action Args
2016-09-11 21:27:22r.david.murraysetrecipients: + r.david.murray, barry, python-dev, Alexander.Kruppa, 天一.何, xZise, jayvdb
2016-09-11 21:27:22r.david.murraysetmessageid: <1473629242.04.0.679911071211.issue19003@psf.upfronthosting.co.za>
2016-09-11 21:27:22r.david.murraylinkissue19003 messages
2016-09-11 21:27:21r.david.murraycreate