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 docs@python, lucca.ruhland, paul.j3, rhettinger
Date 2020-09-01.18:28:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1598984909.38.0.67102302905.issue41684@roundup.psfhosted.org>
In-reply-to
Content
When there are potential conflicts between arguments set by the main parser and those set by a subparser, I often recommend giving the sub ones different "dest" parameters.  Then you can reconcile the different values after parsing.

There's nothing wrong with a bit of post-parsing value checking and adjustment.  The primary purpose of the parser is to identify what the user wants, and secondarily to give useful help and error messages.
History
Date User Action Args
2020-09-01 18:28:29paul.j3setrecipients: + paul.j3, rhettinger, docs@python, lucca.ruhland
2020-09-01 18:28:29paul.j3setmessageid: <1598984909.38.0.67102302905.issue41684@roundup.psfhosted.org>
2020-09-01 18:28:29paul.j3linkissue41684 messages
2020-09-01 18:28:29paul.j3create