Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Is the proposed syntax for this so far. This might be nicer as
X | Y
, but that gets somewhat more magical implementation wise and it's not entirely clear that it's that much better, if at all.What's unclear is whether this syntax is useful without also implying mutual exclusivity. I could imagine for an
int
target,--verbosity 3 -v
might yieldarg == 4
. but ordering would become significant and most other types of inputs wouldn't make sense....granted this is essentially exactly how all of argparse's arguments work (unless there's validation i'm forgetting), relying on you to select metavars that dont conflict in stupid ways...
Ultimately, you'd still be able to opt out of the default behavior by explicitly setting
exclusive_group=None
, for whatever that's worth soooooo 🤷