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 gvanrossum
Recipients akuchling, barry, eric.smith, gvanrossum, jaraco, r.david.murray, vstinner, yselivanov
Date 2015-09-27.23:34:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1443396840.68.0.133668118083.issue25252@psf.upfronthosting.co.za>
In-reply-to
Content
Hm... Since \r\n ends with \n, what exactly would it help to pass in \r\n as the desired line ending? In either case the entire line (including the \r\n) would be returned.

Unless you have a need for treating foo\nbar\r\n as a single line? (But why would you?)  I'm guessing I'm missing something?

No worries about the bug/feature distinction, for asyncio we can do whatever we want (it's still provisional in 3.5).
History
Date User Action Args
2015-09-27 23:34:00gvanrossumsetrecipients: + gvanrossum, barry, akuchling, jaraco, vstinner, eric.smith, r.david.murray, yselivanov
2015-09-27 23:34:00gvanrossumsetmessageid: <1443396840.68.0.133668118083.issue25252@psf.upfronthosting.co.za>
2015-09-27 23:34:00gvanrossumlinkissue25252 messages
2015-09-27 23:34:00gvanrossumcreate