➜

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 nascheme
Recipients Alexander Schrijver, barry, docs@python, ezio.melotti, gregory.p.smith, jwilk, martin.panter, nascheme, python-dev, r.david.murray, scharron, serhiy.storchaka, terry.reedy, vstinner
Date 2018-10-05.06:14:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538720044.32.0.545547206417.issue22232@psf.upfronthosting.co.za>
In-reply-to
Content 
If we introduce a keyword parameter, I think the default of str.splitlines() should be changed to match bytes.splitlines (and match Python 2 str.splitlines()).  I.e. split on \r and \n by default.  I looked through the stdline and I can't find any calls that should actually by splitting on the extra characters.  I will check it again though.

Does anyone have an example of where the current behaviour is actually wanted?
History
Date User Action Args
2018-10-05 06:14:04naschemesetrecipients: + nascheme, barry, terry.reedy, gregory.p.smith, vstinner, jwilk, ezio.melotti, r.david.murray, docs@python, python-dev, martin.panter, serhiy.storchaka, scharron, Alexander Schrijver
2018-10-05 06:14:04naschemesetmessageid: <1538720044.32.0.545547206417.issue22232@psf.upfronthosting.co.za>
2018-10-05 06:14:04naschemelinkissue22232 messages
2018-10-05 06:14:04naschemecreate