[issue16807] argparse group nesting lost on inheritance

Irit Katriel added the comment: Reproduced on 3.11: >>> argparse.ArgumentParser(add_help=False, parents=[parent]).print_help() usage: [--foo FOO] [-a | -b] options: -a -b the group: --foo FOO -- nosy: +iritkatriel versions: +Python 3.10, Python 3.11, Python 3.9 -Python 2.7,

[issue16807] argparse group nesting lost on inheritance

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16807] argparse group nesting lost on inheritance

paul j3 added the comment: The subcommands grouping mechanism proposed in http://bugs.python.org/issue9341 probably does not work with [parents] either. This _add_container_actions method is brittle. It has to know too much about the structure of a parser and its groups. Any change to that

[issue16807] argparse group nesting lost on inheritance

paul j3 added the comment: To put this issue in perspective: - There's nothing in the documentation about nesting a mutually exclusive group in an argument group. - There are prominent notes in the documentation about MEGs not taking title and description. The '_add_container_actions' code

[issue16807] argparse group nesting lost on inheritance

Mark Lawrence added the comment: @Dougal sorry about the delay in getting back to you. -- nosy: +BreamoreBoy, paul.j3 versions: +Python 3.5 -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue16807

[issue16807] argparse group nesting lost on inheritance

New submission from Dougal Sutherland: If you wrap a mutually exclusive group inside an argument group in an argparse.ArgumentParser, and then use parents= to inherit from that parser, the non-exclusive argument group is forgotten in the help output, and the arguments move to the default