Message322538
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. |
|
Date |
User |
Action |
Args |
2018-07-28 10:14:39 | timClicks | set | recipients:
+ timClicks |
2018-07-28 10:14:39 | timClicks | set | messageid: <1532772879.32.0.56676864532.issue34256@psf.upfronthosting.co.za> |
2018-07-28 10:14:39 | timClicks | link | issue34256 messages |
2018-07-28 10:14:39 | timClicks | create | |
|