[issue14763] string.split maxsplit documented incorrectly

Ezio Melotti added the comment: I now documented it in the documentation of str.split too. I left the docstrings alone since they don't need to be as exhaustive as the official documentation, and there's normally no reason to use -1 directly. -- _

[issue14763] string.split maxsplit documented incorrectly

Roundup Robot added the comment: New changeset 0415ecd7b0e3 by Ezio Melotti in branch '2.7': #14763: document default maxsplit value for str.split. http://hg.python.org/cpython/rev/0415ecd7b0e3 New changeset 62659067f5b6 by Ezio Melotti in branch '3.2': #14763: document default maxsplit value f

[issue14763] string.split maxsplit documented incorrectly

Fj added the comment: Thank you. > These functions are anyway deprecated Well, yes, but it's the only place you can get information about the default value of maxsplit, short of looking in the source. Which is kind of wrong. Maybe you can also fix str.split docstring to say "If maxsplit is n

[issue14763] string.split maxsplit documented incorrectly

Ezio Melotti added the comment: I fixed the doc for string.split/rsplit. I didn't change the signature because all the other functions use the old signature convention (the one with []). These functions are anyway deprecated, so I don't think it's worth spending more time improving their do

[issue14763] string.split maxsplit documented incorrectly

Roundup Robot added the comment: New changeset d3ddbad31b3e by Ezio Melotti in branch '2.7': #14763: fix documentation for string.split/rsplit. http://hg.python.org/cpython/rev/d3ddbad31b3e -- nosy: +python-dev ___ Python tracker

[issue14763] string.split maxsplit documented incorrectly

New submission from Fj : string.split documentation says: > The optional third argument maxsplit defaults to 0. If it is nonzero, at most > maxsplit number of splits occur, and the remainder of the string is returned > as the final element of the list (thus, the list will have at most maxsplit