[issue12855] linebreak sequences should be better documented

Changes by Martin Panter : -- stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list maili

[issue12855] linebreak sequences should be better documented

Roundup Robot added the comment: New changeset 2e6fda267a20 by Martin Panter in branch '2.7': Issue #12855: Document what exactly unicode.splitlines() splits on https://hg.python.org/cpython/rev/2e6fda267a20 -- ___ Python tracker

[issue12855] linebreak sequences should be better documented

Alexander Schrijver added the comment: Martin: Yes, it does, thank you. Sorry, I didn't know you where waiting for my approval. -- ___ Python tracker ___ ___

[issue12855] linebreak sequences should be better documented

Martin Panter added the comment: Alexander: does my latest patch linebreakdoc.v5.py2.7.patch address your concerns about the 2.7 documentation? If so, I can push it to the repository. -- ___ Python tracker ___

[issue12855] linebreak sequences should be better documented

Martin Panter added the comment: Here is an updated patch for Python 2, based on Benjamin’s commit, Matthew’s earlier py27 patch, and Alexander’s backport of related changes from Python 3. Let me know what you think. -- nosy: +Alexander Schrijver stage: resolved -> patch review Added f

[issue12855] linebreak sequences should be better documented

Martin Panter added the comment: Reopening to change the Python 2 documentation. A starting point may be Matthew’s patch and/or Alexander’s patch in Issue 22232. -- status: closed -> open ___ Python tracker __

[issue12855] linebreak sequences should be better documented

Roundup Robot added the comment: New changeset 6244a5dbaf84 by Benjamin Peterson in branch '3.4': document what exactly str.splitlines() splits on (closes #12855) https://hg.python.org/cpython/rev/6244a5dbaf84 New changeset 87af6deb5d26 by Benjamin Peterson in branch 'default': merge 3.4 (#12855

[issue12855] linebreak sequences should be better documented

Martin Panter added the comment: Patch v4 adds back the reference to “universal newlines”. I did not alter the doc string, because I don’t think doc strings need to be as detailed as the main documentation. -- Added file: http://bugs.python.org/file38748/linebreakdoc.v4.py3.5.patch __

[issue12855] linebreak sequences should be better documented

R. David Murray added the comment: SMRUTI: \f is the python escape code for the ASCII formfeed character. It is the handling of that ASCII character (among others) that this issue is discussing. -- nosy: +r.david.murray ___ Python tracker

[issue12855] linebreak sequences should be better documented

SMRUTI RANJAN SAHOO added the comment: i think in this, "line \fone\nline two\n" ,the space after line taking some garbage value or you can say hex value of "\". so that's why that is showing some hex value. if you write "\n " instead of"\" then you can't find that hex value. i attached my id

[issue12855] linebreak sequences should be better documented

Martin Panter added the comment: Note to self, or anyone else handling this patch: See for further improvement ideas: * Might be good to bring back the reference to universal newlines, but say it accepts additional line boundaries * Terry also sug

[issue12855] linebreak sequences should be better documented

Martin Panter added the comment: Posting linebreakdoc.v3.py3.5.patch: * Rebased onto recent “default” (3.5) branch * Add missing 1C–1E codes * Dropped reference to “universal newlines”, since that only handles CRs and LFs as I understand it The newlines are already tested by test_unicodedata.

[issue12855] linebreak sequences should be better documented

Martin Panter added the comment: Any reason why characters 1C–1E are excluded? -- nosy: +vadmium ___ Python tracker ___ ___ Python-bug

[issue12855] linebreak sequences should be better documented

Changes by Zachary Ware : -- stage: -> patch review versions: +Python 3.4, Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker ___

[issue12855] linebreak sequences should be better documented

David Halter added the comment: I would vote for the inclusion of that patch. I just stumbled over this. -- nosy: +davidhalter ___ Python tracker ___

[issue12855] linebreak sequences should be better documented

Changes by Matthew Boehm : Added file: http://bugs.python.org/file23077/linebreakdoc.v2.py32.patch ___ Python tracker ___ ___ Python-bugs-list

[issue12855] linebreak sequences should be better documented

Matthew Boehm added the comment: I've attached a patch for 2.7 and will attach one for 3.2 in a minute. I built the docs for both 2.7 and 3.2 and verified that there were no warnings and that the resulting web pages looked okay. Things to consider: * Placement of unicode.splitlines() method:

[issue12855] linebreak sequences should be better documented

STINNER Victor added the comment: > 1. On the howto/unicode.html > 2. Somewhere in the stdtypes.html#typesseq description (maybe with other > notes at the bottom) > 3. As a note to the stdtypes.html#str.splitlines method description (where it > is in the previous patch.) (3) is the best place

[issue12855] linebreak sequences should be better documented

Matthew Boehm added the comment: I can fix the patch to list all the unicode line boundaries. The three places I've considered putting it are: 1. On the howto/unicode.html 2. Somewhere in the stdtypes.html#typesseq description (maybe with other notes at the bottom) 3. As a note to the stdty

[issue12855] linebreak sequences should be better documented

Changes by STINNER Victor : -- components: +Unicode versions: +Python 3.2, Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mail

[issue12855] linebreak sequences should be better documented

STINNER Victor added the comment: > Would it be better to put this note in a different place? You may just say that StreamReader.readline() uses unicode.splitlines(), and so point to unicode.splitlines() doc (use :meth:`unicode.splitlines` syntax). unicode.splitlines() is now well documented:

[issue12855] linebreak sequences should be better documented

Matthew Boehm added the comment: I've attached a patch for python2.7 that adds a small not to library/stdtypes.html#str.splitlines explaining which sequences are treated as line breaks: """ Note: Python recognizes "\r", "\n", and "\r\n" as line boundaries for strings. In addition to these, U