Robert Leenders added the comment:
Chris, you said (in the review) Hmm, since this is for maintenance releases
... This change could cause working code to no longer work.
I understood from our original message that you wanted it to change since it is
inconsistent. I vote for changing it (so
Changes by Robert Leenders robertleender...@gmail.com:
Removed file: http://bugs.python.org/file28766/argparse-v2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16970
Changes by Robert Leenders robertleender...@gmail.com:
Added file: http://bugs.python.org/file28767/argparse-v2.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16970
Robert Leenders added the comment:
Attached is a patch which solves these problems and adds test cases of Chris
Jerdonek. When nargs is negative the same ValueError is raised as when nargs is
zero. Also when nargs is any other invalid value a ValueError(invalid value
for nargs) is raised.
I
New submission from Robert Leenders:
There is a value for nargs: PARSER=A... which is not documented at
http://docs.python.org/3.4/library/argparse.html#nargs. The docstring for the
action class in argparse.py also does not list PARSER as a valid value for
nargs.
In argparse.py on line 2199
Robert Leenders added the comment:
The new issue about PARSER can be found here: http://bugs.python.org/issue16988
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16970
