-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-41255: handle argparse errors with exit_on_error=False consistently #27295
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
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA). CLA MissingOur records indicate the following people have not signed the CLA: For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. If you have recently signed the CLA, please wait at least one business day You can check yourself to see if the CLA has been received. Thanks again for the contribution, we look forward to reviewing it! |
This PR is stale because it has been open for 30 days with no activity. |
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.
Works for me:
Ran 1658 tests in 2.516s
OK
Simple bug mentioned case too!
Nice work
Trigger CLA. A |
This PR is stale because it has been open for 30 days with no activity. |
Thank you for your contribution @joshmeranda. I apologize for the fact that this PR was neglected for a long time. The problem has already been solved in another way. |
bpo-41255
When unknown arguments are passed to
parse_args
or required arguments not passed to eitherparse_args
orparse_known_args
argpase exits despiteexit_on_error=False
. This is not very intuitive, instead any error parsing arguments should result in anArgumentError
which can be handled by the user.https://bugs.python.org/issue41255