This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author paul.j3
Recipients ThatXliner, paul.j3, rhettinger
Date 2020-10-14.03:13:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602645203.55.0.152526301429.issue42023@roundup.psfhosted.org>
In-reply-to
Content
I'm not following this request either, especially the colored part.

However, I can imagine adding a variable that gives the user full control over the action-invocation.  In:

    argparse.HelpFormatter._format_action_invocation method.

Currently it accepts the metavar (but not the tuple version) for a positional, but for optionals constructs:

  -s ARGS, --long ARGS

This can be quite long and ugly if the ARGS is a long choices, or there are many flag alternatives.  A number of SO users have asked for something simpler, usually with just on flag or

  -s, --long ARGS

There may even be a bug/issue(s) related to this already.
History
Date User Action Args
2020-10-14 03:13:23paul.j3setrecipients: + paul.j3, rhettinger, ThatXliner
2020-10-14 03:13:23paul.j3setmessageid: <1602645203.55.0.152526301429.issue42023@roundup.psfhosted.org>
2020-10-14 03:13:23paul.j3linkissue42023 messages
2020-10-14 03:13:23paul.j3create