You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=Nonecreated_at=<Date2017-03-28.17:43:18.709>labels= ['type-feature', 'library']
title='argparse mutex group should allow mandatory parameters'updated_at=<Date2017-03-28.17:43:18.709>user='https://bugs.python.org/MarkNolan'
I see elsewhere, and from use, that a mutex group will not support mandatory positional parameters.
TBH, I don't understand why this should be any different from any other option, but if it must, then I think it should follow the 'required' parameter of the mutex.
So, it should be possible to have a mutex group where one option must be chosen and that option must have positional parameters.
(My first post here. Not sure of any other way to discuss with the argparse development group. Point me somewhere else if appropriate).
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: