-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
GH-79714: Add mention of stderr for clarity to ArgumentParser.exit() #123932
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Thanks @savannahostrowski for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
Thanks @savannahostrowski for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12. |
…xit() (pythonGH-123932) (cherry picked from commit 5f5c0b9) Co-authored-by: Savannah Ostrowski <[email protected]>
Sorry, @savannahostrowski and @serhiy-storchaka, I could not cleanly backport this to
|
GH-124331 is a backport of this pull request to the 3.13 branch. |
The conflict is because |
…arser.exit() (pythonGH-123932) (cherry picked from commit 5f5c0b9) Co-authored-by: Savannah Ostrowski <[email protected]>
GH-124356 is a backport of this pull request to the 3.12 branch. |
This PR adds a tiny clarification about how
ArgumentParser.exit()
prints to stderr.📚 Documentation preview 📚: https://cpython-previews--123932.org.readthedocs.build/