[3.13] gh-121652: Handle allocate_weakref returning NULL (GH-121653)#121721
Merged
colesbury merged 1 commit intopython:3.13from Jul 13, 2024
Merged
[3.13] gh-121652: Handle allocate_weakref returning NULL (GH-121653)#121721colesbury merged 1 commit intopython:3.13from
allocate_weakref returning NULL (GH-121653)#121721colesbury merged 1 commit intopython:3.13from
Conversation
This was referenced Jul 13, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
allocate_weakrefmay return NULL when out of memory. We need tohandle that case and propagate the error.
(cherry picked from commit a640a60)
Co-authored-by: Sam Gross colesbury@gmail.com
weakrefobject.cdoesn't handleallocate_weakreffailures #121652