NotificationsYou must be signed in to change notification settings
Fork33.4k
Star69.8k

gh-86463: Fix default prog in subparsers if usage is used in the parent parser#124532

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Closed

serhiy-storchaka wants to merge2 commits intopython:mainfromserhiy-storchaka:argparse-subparser-custom-usage

Closed

gh-86463: Fix default prog in subparsers if usage is used in the parent parser#124532

serhiy-storchaka wants to merge2 commits intopython:mainfromserhiy-storchaka:argparse-subparser-custom-usage

Conversation

Copy link

Member

serhiy-storchaka commentedSep 25, 2024•
edited by github-actionsbot
Loading

The placeholder '...' is now used as the prog prefix in subparsers if a custom usage is specified in the parent parser and prog is not specified in the subparser.

Previously the full custom usage of the parent parser was used as the prog prefix in subparsers.

Issue:[argparse] Bad error message formatting when using custom usage text #86463

📚 Documentation preview 📚:https://cpython-previews--124532.org.readthedocs.build/

pythongh-86463: Fix default prog in subparsers if usage is used in th…

f7d939b

…e parent parserThe placeholder '...' is now used as the prog prefix in subparsersif a custom usage is specified in the parent parser and prog is notspecified in the subparser.Previously the full custom usage of the parent parser was used asthe prog prefix in subparsers.