Skip to content

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

Closed
serhiy-storchaka wants to merge 2 commits intopython:mainfrom
serhiy-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 merge 2 commits intopython:mainfrom
serhiy-storchaka:argparse-subparser-custom-usage

Conversation

@serhiy-storchaka
Copy link
Member

@serhiy-storchaka serhiy-storchaka commented Sep 25, 2024

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.


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

…e parent parser

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.
@serhiy-storchaka serhiy-storchaka deleted the argparse-subparser-custom-usage branch November 22, 2024 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant