paul j3 <[email protected]> added the comment:
A mutually_exclusive_group is not an argument_group. It affects parsing and
the usage, but does nothing in the help lines.
A mutually_exclusive_group may be nested in an argument_group if you want
another group title.
g1 = parser.add_argument_group('My Required Group')
g2 = g1.add_mutually_exclusive_group(....)
Groups are not really designed for nesting, but this is one case the nesting
works and is useful. Nesting, to the extent it works, is simple a consequence
of inheritance from the _Argument_Container class.
Changing the title of the default action group is always an option,
mutually_exclusive or not. Other bug/issues have suggest changing that title
at creation time, or giving the user a choice (maybe even defining 3 default
groups). But for now we recommend creating your own argument group(s) if you
don't like the titles of the default one(s).
So no, I don't think anything should be changed simply because a
mutually_exclusive group is marked as required.
----------
nosy: +paul.j3
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue39197>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
