[issue15554] correct and clarify str.splitlines() documentation

R. David Murray added the comment: Thanks for sticking with it. -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue15554] correct and clarify str.splitlines() documentation

Roundup Robot added the comment: New changeset 768b188262e7 by R David Murray in branch '3.2': #15554: clarify splitlines/split differences. http://hg.python.org/cpython/rev/768b188262e7 New changeset 0d6eea2330d0 by R David Murray in branch 'default': Merge #15554: clarify splitlines/split diff

[issue15554] correct and clarify str.splitlines() documentation

Chris Jerdonek added the comment: Here you go. Thanks again. -- Added file: http://bugs.python.org/file26709/issue-15554-4.patch ___ Python tracker ___ _

[issue15554] correct and clarify str.splitlines() documentation

R. David Murray added the comment: Good point. Difference paragraph after the example would be best, I think. -- ___ Python tracker ___ _

[issue15554] correct and clarify str.splitlines() documentation

Chris Jerdonek added the comment: > I think the problem really is that 'split' has such radically different > behavior when given an argument as opposed to when it isn't. Yep, the split() documentation is much more involved because of that. > Please move the keeplines discussion back up into t

[issue15554] correct and clarify str.splitlines() documentation

R. David Murray added the comment: Ah, I read too quickly before. But that expression "when a delimiter string *sep* is given" is hard to wrap ones head around in this context. I think the problem really is that 'split' has such radically different behavior when given an argument as opposed

[issue15554] correct and clarify str.splitlines() documentation

Changes by R. David Murray : -- Removed message: http://bugs.python.org/msg167557 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue15554] correct and clarify str.splitlines() documentation

R. David Murray added the comment: Ah, I read too quickly before. But that expression "when a delimiter string *sep* is given" is hard to wrap ones head around in this context. I think the problem really is that 'split' has such radically different behavior when given an argument as opposed

[issue15554] correct and clarify str.splitlines() documentation

Chris Jerdonek added the comment: > in the patch it now sounds like you are saying that ''.splitlines() does not > return the same result as ''.split() when in fact it does. The two differences occur only when split() is passed a separator. split() uses a different algorithm when no separator

[issue15554] correct and clarify str.splitlines() documentation

Changes by Terry J. Reedy : -- nosy: +terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue15554] correct and clarify str.splitlines() documentation

R. David Murray added the comment: Ah, now I see what you are talking about. Yes, your revision in the comment is clearer; but, unless I read it wrong, in the patch it now sounds like you are saying that ''.splitlines() does not return the same result as ''.split() when in fact it does. I wo

[issue15554] correct and clarify str.splitlines() documentation

Chris Jerdonek added the comment: Attaching patch with simplified wording in response to R. David Murray's feedback. In particular, "a terminal line break does not delimit an additional empty line" -> "a terminal line break does not result in an extra line." -- Added file: http://bugs

[issue15554] correct and clarify str.splitlines() documentation

Chris Jerdonek added the comment: > I wasn't really happy with the addition of that sentence about split in the > first place. I think the instinct to put that sentence in there is a good one. It is a key, perhaps subtle difference. > I don't understand what your splitlines examples are tryi

[issue15554] correct and clarify str.splitlines() documentation

R. David Murray added the comment: Sigh. ;) At this point in my Python programming I intuitively understand what splitlines does, but every time we try to explain it in detail it gets messier and messier. I wasn't really happy with the addition of that sentence about split in the first place

[issue15554] correct and clarify str.splitlines() documentation

New submission from Chris Jerdonek: The documentation for str.splitlines()-- http://docs.python.org/dev/library/stdtypes.html#str.splitlines includes a statement that is not quite correct: "Unlike split(), if the string ends with line boundary characters the returned list does not have an emp