-
-
Notifications
You must be signed in to change notification settings - Fork 34k
bpo-35284: Fix the error handling in the compiler's compiler_call() #10625
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
bpo-35284: Fix the error handling in the compiler's compiler_call() #10625
Conversation
compiler_call() needs to check if an error occurred during the maybe_optimize_method_call() call.
|
Good catch! 👏 It is hard to notice this error. 🕵️♂️ How did you find it? Do you mind to add a comment to |
|
Ping. |
|
@ZackerySpytz just in case you didn't see the "ping" from Serhiy. |
|
I saw it. |
|
Hi, @serhiy-storchaka. Thank you for updating this PR. However, it seems that there is an error in the comment that you added. I will edit the comment. |
|
Thanks @ZackerySpytz for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7. |
|
Sorry, @ZackerySpytz and @serhiy-storchaka, I could not cleanly backport this to |
…ythonGH-10625) compiler_call() needs to check if an error occurred during the maybe_optimize_method_call() call. (cherry picked from commit 97f5de0)
|
GH-12496 is a backport of this pull request to the 3.7 branch. |
|
Hi, @serhiy-storchaka. I've created a backport PR for 3.7. |
compiler_call() needs to check if an error occurred during the
maybe_optimize_method_call() call.
https://bugs.python.org/issue35284