➜

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 jeffknupp
Recipients Robert, bethard, chris.jerdonek, docs@python, jeffknupp
Date 2013-01-18.15:11:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1358521861.86.0.384728687708.issue16988@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2013-01-18 15:11:01jeffknuppsetrecipients: + jeffknupp, bethard, chris.jerdonek, docs@python, Robert
2013-01-18 15:11:01jeffknuppsetmessageid: <1358521861.86.0.384728687708.issue16988@psf.upfronthosting.co.za>
2013-01-18 15:11:01jeffknupplinkissue16988 messages
2013-01-18 15:11:01jeffknuppcreate