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 timClicks
Recipients timClicks
Date 2018-07-28.10:14:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1532772879.32.0.56676864532.issue34256@psf.upfronthosting.co.za>
In-reply-to
Content
Hello,

I apologize if this is expected behavior, however it doesn't appear to be documented.

>>> "single\x1eline\x1estring".splitlines()
['single', 'line', 'string']

The glossary refers to the universal newlines as:


> universal newlines
>    A manner of interpreting text streams in which all of the 
>    following are recognized as ending a line: the Unix end-of-line
>    convention '\n', the Windows convention '\r\n', and the old 
>    Macintosh convention '\r'. See PEP 278 and PEP 3116, as well as 
>    bytes.splitlines() for an additional use.
https://docs.python.org/3/glossary.html#term-universal-newlines

According to Wikipedia, pre-POSIX QNX uses `\x1e` as a newline (https://en.wikipedia.org/wiki/Newline#Representation), but I don't think that it should be treated as the default.
History
Date User Action Args
2018-07-28 10:14:39timClickssetrecipients: + timClicks
2018-07-28 10:14:39timClickssetmessageid: <1532772879.32.0.56676864532.issue34256@psf.upfronthosting.co.za>
2018-07-28 10:14:39timClickslinkissue34256 messages
2018-07-28 10:14:39timClickscreate