[issue16970] argparse: bad nargs value raises misleading message

2013-01-18 Thread Robert Leenders
Changes by Robert Leenders : Added file: http://bugs.python.org/file28767/argparse-v2.patch ___ Python tracker <http://bugs.python.org/issue16970> ___ ___ Python-bug

[issue16970] argparse: bad nargs value raises misleading message

2013-01-18 Thread Robert Leenders
Changes by Robert Leenders : Removed file: http://bugs.python.org/file28766/argparse-v2.patch ___ Python tracker <http://bugs.python.org/issue16970> ___ ___ Python-bug

[issue16970] argparse: bad nargs value raises misleading message

2013-01-18 Thread Robert Leenders
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

[issue16970] argparse: bad nargs value raises misleading message

2013-01-17 Thread Robert Leenders
Robert Leenders added the comment: The new issue about PARSER can be found here: http://bugs.python.org/issue16988 -- ___ Python tracker <http://bugs.python.org/issue16

[issue16988] argparse: PARSER option for nargs not documented

2013-01-17 Thread Robert Leenders
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.

[issue16970] argparse: bad nargs value raises misleading message

2013-01-17 Thread Robert Leenders
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")