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 TurboTurtle, paul.j3, rhettinger
Date 2020-11-10.19:44:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1605037458.89.0.327519378282.issue42297@roundup.psfhosted.org>
In-reply-to
Content
We could look into using a different more compact 'prog' for these error messages.

Currently the subparser 'prog' uses the main prog plus positionals plus the subparser name.  The goal is to construct a subparser usage that reflects required input.  

This is fine for the usage line, but could be too verbose for some errors.  In an error, the 'prog' just helps identify which argument has problems, and doesn't need the extra usage information.   Most of the time that isn't an issue, since we don't use positional much in the main parser (and when used can't have variable nargs).

But I don't have immediate ideas as to what can be conveniently (and safely) changed.
History
Date User Action Args
2020-11-10 19:44:18paul.j3setrecipients: + paul.j3, rhettinger, TurboTurtle
2020-11-10 19:44:18paul.j3setmessageid: <1605037458.89.0.327519378282.issue42297@roundup.psfhosted.org>
2020-11-10 19:44:18paul.j3linkissue42297 messages
2020-11-10 19:44:18paul.j3create