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 ygingras
Recipients paul.j3, rhettinger, ygingras
Date 2020-10-10.13:07:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1602335257.35.0.403890880917.issue41980@roundup.psfhosted.org>
In-reply-to
Content
Raymond, I would love to submit the PR if we reach a consensus on what the new message should be.  I'm a bit out of touch with how things work these days.  Is Github the best place to submit the PR?

Paul, very good digging!  Reading the coding and running a few examples, I understand that the ``prog`` of the subparser is always the name of the main program with the name of the subcommand *unless* a usage string is supplied, in which case it overrides prog.  I suspect that the intent is to favour the programmer supplied usage string and that copying the usage string in the prog of the subparser is an implementation detail.   I think we can reword the documentation to describe the expected behavior with more emphasis on the common cases.
History
Date User Action Args
2020-10-10 13:07:37ygingrassetrecipients: + ygingras, rhettinger, paul.j3
2020-10-10 13:07:37ygingrassetmessageid: <1602335257.35.0.403890880917.issue41980@roundup.psfhosted.org>
2020-10-10 13:07:37ygingraslinkissue41980 messages
2020-10-10 13:07:37ygingrascreate