[issue9341] allow argparse subcommands to be grouped

paul j3 added the comment: This patch probably won't work with [parents]. see http://bugs.python.org/issue16807 -- ___ Python tracker ___ ___

[issue9341] allow argparse subcommands to be grouped

paul j3 added the comment: This patch accomplishes this task by adding a _PseudoGroup class to _SubParsersAction. It's like the _ChoicesPseudoAction except that it maintains its own _choices_actions list. It takes advantage of the fact that formatter._format_actions is recursive when it com

[issue9341] allow argparse subcommands to be grouped

Changes by Mark Lawrence : -- nosy: +paul.j3 versions: +Python 2.7, Python 3.5 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list

[issue9341] allow argparse subcommands to be grouped

Changes by Phil Connell : -- nosy: +pconnell ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue9341] allow argparse subcommands to be grouped

Changes by Éric Araujo : -- nosy: +merwok resolution: -> accepted versions: +Python 3.2 ___ Python tracker ___ ___ Python-bugs-list ma

[issue9341] allow argparse subcommands to be grouped

New submission from Steven Bethard : [Moved from http://code.google.com/p/argparse/issues/detail?id=53] It's currently not possible to have subcommands formatted in groups, e.g. instead of: subcommands: {a,b,c,d,e} a a subcommand help b b subcommand help c