Martin Panter added the comment:
Thanks to Issue 11807, the documentation now lists “metavar”. (However, it
looks like a positional argument, rather than keyword-only, and its use seems
to be discouraged, but those issues are not specific to “metavar”.)
Some points specific to “metavar” that
Changes by Chris Jerdonek chris.jerdo...@gmail.com:
--
nosy: +chris.jerdonek
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14039
___
___
Chris Jerdonek added the comment:
Have you tried setting the metavar property on the return value of
add_subparsers()? I tried this, and it seems to work.
It looks like the logic for _metavar_formatter() is the same no matter what the
action type (specifically _SubParsersAction in this
Chris Jerdonek added the comment:
Actually, it looks like add_subparsers() may already support passing a metavar
argument, but it's just not documented?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14039
Changes by Berker Peksag berker.pek...@gmail.com:
--
versions: +Python 3.4 -Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14039
___
___
Changes by Kushal Das kushal...@gmail.com:
--
nosy: +kushaldas
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14039
___
___
Python-bugs-list
Changes by Tshepang Lekhonkhobe tshep...@gmail.com:
--
nosy: +tshepang
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14039
___
___
New submission from Nick Coghlan ncogh...@gmail.com:
Currently, using add_subparsers() means that the entire list of subcommands is
added to the main usage message. This gets rather unwieldy when there are a lot
of subcommands.
It would be nice if the add_subparsers() method accepted a
