Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32.2k
gh-121018: Fix more cases of exiting in argparse when exit_on_error=False#121056
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
gh-121018: Fix more cases of exiting in argparse when exit_on_error=False#121056
Uh oh!
There was an error while loading.Please reload this page.
Conversation
…rror=False* parse_intermixed_args() now raises ArgumentError instead of calling error() if exit_on_error is false.* Internal code now always raises ArgumentError instead of calling error(). It is then caught at higher level and error() is called if exit_on_error is true.
81a654a
intopython:mainUh oh!
There was an error while loading.Please reload this page.
Thanks@serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
Sorry,@serhiy-storchaka, I could not cleanly backport this to
|
Sorry,@serhiy-storchaka, I could not cleanly backport this to
|
…it_on_error=False (pythonGH-121056)* parse_intermixed_args() now raises ArgumentError instead of calling error() if exit_on_error is false.* Internal code now always raises ArgumentError instead of calling error(). It is then caught at the higher level and error() is called if exit_on_error is true.(cherry picked from commit81a654a)Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
GH-121128 is a backport of this pull request to the3.13 branch. |
…it_on_error=False (pythonGH-121056)* parse_intermixed_args() now raises ArgumentError instead of calling error() if exit_on_error is false.* Internal code now always raises ArgumentError instead of calling error(). It is then caught at the higher level and error() is called if exit_on_error is true.(cherry picked from commit81a654a)Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
GH-121129 is a backport of this pull request to the3.12 branch. |
…error=False (GH-121056) (GH-121129)* parse_intermixed_args() now raises ArgumentError instead of calling error() if exit_on_error is false.* Internal code now always raises ArgumentError instead of calling error(). It is then caught at the higher level and error() is called if exit_on_error is true.(cherry picked from commit81a654a)
…error=False (GH-121056) (GH-121128)* parse_intermixed_args() now raises ArgumentError instead of calling error() if exit_on_error is false.* Internal code now always raises ArgumentError instead of calling error(). It is then caught at the higher level and error() is called if exit_on_error is true.(cherry picked from commit81a654a)
…rror=False (pythonGH-121056)* parse_intermixed_args() now raises ArgumentError instead of calling error() if exit_on_error is false.* Internal code now always raises ArgumentError instead of calling error(). It is then caught at the higher level and error() is called if exit_on_error is true.
…rror=False (pythonGH-121056)* parse_intermixed_args() now raises ArgumentError instead of calling error() if exit_on_error is false.* Internal code now always raises ArgumentError instead of calling error(). It is then caught at the higher level and error() is called if exit_on_error is true.
…rror=False (pythonGH-121056)* parse_intermixed_args() now raises ArgumentError instead of calling error() if exit_on_error is false.* Internal code now always raises ArgumentError instead of calling error(). It is then caught at the higher level and error() is called if exit_on_error is true.
Uh oh!
There was an error while loading.Please reload this page.