| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
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! |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
There was a problem hiding this comment.
Works for me:
Ran 1658 tests in 2.516s
OK
Simple bug mentioned case too!
Nice work
Sorry, something went wrong.
|
Trigger CLA. A |
Sorry, something went wrong.
|
This PR is stale because it has been open for 30 days with no activity. |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
bpo-41255
When unknown arguments are passed to parse_args or required arguments not passed to either parse_args or parse_known_args argpase exits despite exit_on_error=False. This is not very intuitive, instead any error parsing arguments should result in an ArgumentError which can be handled by the user.
https://bugs.python.org/issue41255