[Python-Dev] PEP 385: the eol-type issue
Antoine Pitrou
solipsis at pitrou.net
Thu Aug 6 10:51:29 CEST 2009
More information about the Python-Dev mailing list
Thu Aug 6 10:51:29 CEST 2009
- Previous message: [Python-Dev] PEP 385: the eol-type issue
- Next message: [Python-Dev] PEP 385: the eol-type issue
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
M.-A. Lemburg <mal <at> egenix.com> writes: > > Please file a bug report for this. f.readlines() (or rather > the io layer) should be using Py_UNICODE_ISLINEBREAK(ch) > for detecting line break characters. Actually, no. It has been designed from the start to only recognize the "standard" line break representations found in common formats/protocols (CR, LF and CR+LF). People wanting to split on arbitrary unicode line breaks should use str.splitlines(). Regards Antoine.
- Previous message: [Python-Dev] PEP 385: the eol-type issue
- Next message: [Python-Dev] PEP 385: the eol-type issue
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list