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 calestyo
Recipients calestyo, paul.j3, rhettinger
Date 2021-02-21.23:52:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Well but if that's anyway one of its actual major use cases, wouldn't it make sense to properly support it?

Especially when one has a large set of identical options (which is then even more likely to also include mutually exclusive ones) such a feature seems to be pretty useful to prevent bloated code by copy&pasting large number of lines of identical argument parsing code.

argparse is really nice and powerful,... and enables people to make clean argparsing code, but it seems a few quite features which are quite often asked for miss, like e.g. #11354 or that one can arbitrarily group mutually exclusive options like:

<mutually exclusive>
<(mutually exclusive>

Anyway, feel free to close if you don't like supporting mutually exclusive groups with parents.

Date User Action Args
2021-02-21 23:52:23calestyosetrecipients: + calestyo, rhettinger, paul.j3
2021-02-21 23:52:23calestyosetmessageid: <>
2021-02-21 23:52:23calestyolinkissue43259 messages
2021-02-21 23:52:23calestyocreate