Message180195
This is not a bug.
The 'PARSER' nargs choice is an implementation detail as a way to handle subparsers. The parser needs to know that the first value should be handled, but everything that follows will be handled by the subparser.
By using a subparser, you're effectively using 'PARSER', but it wouldn't make sense to allow 'PARSER' to be set directly as it only makes sense when used in conjunction with a subparser. |
|
Date |
User |
Action |
Args |
2013-01-18 15:11:01 | jeffknupp | set | recipients:
+ jeffknupp, bethard, chris.jerdonek, docs@python, Robert |
2013-01-18 15:11:01 | jeffknupp | set | messageid: <1358521861.86.0.384728687708.issue16988@psf.upfronthosting.co.za> |
2013-01-18 15:11:01 | jeffknupp | link | issue16988 messages |
2013-01-18 15:11:01 | jeffknupp | create | |
|