Sandro Tosi sandro.t...@gmail.com added the comment:
That's interesting: do we have a place where we explain how to read the doc? I
mean, a place were we can provide example/explain how we write docs, so f.e.:
str.rsplit([sep[, maxsplit]])
is a description for a method that could accept 2
Éric Araujo mer...@netwok.org added the comment:
The description for the function directive is at
http://docs.python.org/dev/documenting/markup.html However, I’m not sure
whether the doc is accurate, since there was a switch from spam([style]) to
spam(style=None) some time ago, for example
New submission from Dave Abrahams d...@boostpro.com:
Based on the rsplit documentation, I'd expect
'foo bar'.rsplit(maxsplit=1)
to work. This is probably a much bigger problem than just rsplit, i.e. I doubt
there is a policy about whether documented parameter names need to be usable as
Changes by Brett Cannon br...@python.org:
--
keywords: +easy
stage: - unit test needed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8626
___
___
Antoine Pitrou pit...@free.fr added the comment:
This is more of a documentation issue than anything else. The fact that the
argument is named maxsplit and accepts a default value doesn't mean it's
usable as a keyword argument. It would be difficult to document a parameter
without giving it a
