Message 180195 - Python tracker

➜

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	<[email protected]>
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.

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:01	jeffknupp	set	recipients: + jeffknupp, bethard, chris.jerdonek, docs@python, Robert
2013-01-18 15:11:01	jeffknupp	set	messageid: <[email protected]>
2013-01-18 15:11:01	jeffknupp	link	issue16988 messages
2013-01-18 15:11:01	jeffknupp	create