-
-
Notifications
You must be signed in to change notification settings - Fork 32.9k
bpo-45716: Improve the error message when using True/False/None as keywords in a call #29413
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
The patch looks good to me! |
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.
I like this :)
Thanks @pablogsal for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10. |
Sorry, @pablogsal, I could not cleanly backport this to |
…e as keywords in a call (pythonGH-29413). (cherry picked from commit e2d6563) Co-authored-by: Pablo Galindo Salgado <[email protected]>
GH-29428 is a backport of this pull request to the 3.10 branch. |
|
…e as keywords in a call (GH-29413). (GH-29428) (cherry picked from commit e2d6563) Co-authored-by: Pablo Galindo Salgado <[email protected]>
https://bugs.python.org/issue45716