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 belopolsky, doerwalter, ezio.melotti, lemburg, nascheme, r.david.murray, serhiy.storchaka, vstinner, wpk, xtreak
Date 2018-10-05.06:09:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I just found bug #22232 myself but thanks for pointing it out.

> changing the behavior unconditionally is not an option

At this point, I disagree.  If I do a search on the web, lots of pages referring to str.splitlines() seem it imply that is splits only on \r and \n.  For Python 2 that was correct.  I think most people would be surprised by the Python 3 behaviour.

I looked through the Python stdlib and marked any place str.splitlines() was used.  I have more research to do yet but I think nearly all of these cases will work better (or perhaps correctly) if str.splitlines is changed.
Date User Action Args
2018-10-05 06:09:20naschemesetrecipients: + nascheme, lemburg, doerwalter, belopolsky, vstinner, ezio.melotti, r.david.murray, serhiy.storchaka, wpk, xtreak
2018-10-05 06:09:20naschemesetmessageid: <>
2018-10-05 06:09:20naschemelinkissue18291 messages
2018-10-05 06:09:20naschemecreate