-
-
Notifications
You must be signed in to change notification settings - Fork 33.4k
gh-121660: Fix ga_getitem by explicitly checking for NULL result
#121661
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
JelleZijlstra
left a comment
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.
Looks good. It appears this can only happen if there is a memory failure (e.g., PyTuple_Pack fails), so it's not feasible to test for it, but we should still fix this.
|
Thanks @sobolevn for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
…esult (pythonGH-121661) (cherry picked from commit bb802db) Co-authored-by: sobolevn <[email protected]>
…esult (pythonGH-121661) (cherry picked from commit bb802db) Co-authored-by: sobolevn <[email protected]>
|
GH-121761 is a backport of this pull request to the 3.13 branch. |
|
GH-121762 is a backport of this pull request to the 3.12 branch. |
ga_getitemcan fail ifPy_GenericAliasreturnsNULL#121660