➜

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 martin.panter
Recipients Jeremy.Hylton, barry, gvanrossum, martin.panter, r.david.murray, serhiy.storchaka
Date 2017-03-26.12:08:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1490530123.95.0.136286121265.issue18022@psf.upfronthosting.co.za>
In-reply-to
Content 
The double equals "==" case for the “quopri” implementation in Python is now consistent with the others thanks to the fix in Issue 23681 (see also Issue 21511).

According to Issue 20121, the quopri (Python) implementation only supports LF (\n) characters as line breaks, and the binascii (C) implementation also supports CRLF. So I agree that the whitespace-before-newline case "= \n" is a genuine bug (see Issue 16473). But the CR case "=\r" is not supported because neither quopri nor binascii support universal newlines or CR line breaks on their own.
History
Date User Action Args
2017-03-26 12:08:43martin.pantersetrecipients: + martin.panter, gvanrossum, barry, r.david.murray, Jeremy.Hylton, serhiy.storchaka
2017-03-26 12:08:43martin.pantersetmessageid: <1490530123.95.0.136286121265.issue18022@psf.upfronthosting.co.za>
2017-03-26 12:08:43martin.panterlinkissue18022 messages
2017-03-26 12:08:43martin.pantercreate