This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paul.j3
Recipients BreamoreBoy, Jason.Baker, bethard, eric.araujo, paul.j3
Date 2013-04-25.04:31:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This is a revision of yesterday's patch.  It includes a couple of test cases that check that parser, groups, and exclusive groups all produce the error message.

I also changed the metavar tuple case to return an ArgumentError, and changed accordingly.  (this metavar testing was added in

This issue overlaps with, 'argparse: bad nargs value raises misleading message'.  There, though, the focus is  more on the error message when nargs=0.  While nargs<1 might not make much sense, it technically does not break anything.
Date User Action Args
2013-04-25 04:31:58paul.j3setrecipients: + paul.j3, bethard, eric.araujo, Jason.Baker, BreamoreBoy
2013-04-25 04:31:58paul.j3setmessageid: <>
2013-04-25 04:31:58paul.j3linkissue9849 messages
2013-04-25 04:31:58paul.j3create