paul j3 added the comment:
A notational point - you are adding a subparser, not an argument, to the
subparsers action.
Why would a user want to use `help=argparse.SUPPRESS`, as opposed to simply
omitting the `help` parameter? The effect would be the same as your patch.
Another possibility is to interpret this SUPPRESS as meaning, omit the
subparser (and it's aliases?) from the choices list(s) as well. In other
words, make this an entirely stealth choice.
usage: test [-h] {foo} ...
positional arguments:
{foo}
foo This is help for foo
...
'test bar -h' would still display a help for that subparser (unless given a
`add_help=False` parameter).
I don't know how much work this stronger SUPPRESS would required, or whether
such an interpretation would be intuitive to most users. There isn't a
mechanism to omit a regular argument from the usage, so why should there be a
mechanism for omitting a subparsers choice from usage?
With the weaker interpretation, this patch fills in a hole in the logic, but
doesn't add any functionality (that I can think of).
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue22848>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
