Skip to content

[3.13] gh-121652: Handle allocate_weakref returning NULL (GH-121653) #121721

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jul 13, 2024
Merged

[3.13] gh-121652: Handle allocate_weakref returning NULL (GH-121653) #121721

merged 1 commit into from
Jul 13, 2024

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Jul 13, 2024 •
edited by bedevere-app bot
Loading

The allocate_weakref may return NULL when out of memory. We need to
handle that case and propagate the error.
(cherry picked from commit a640a60)

Co-authored-by: Sam Gross colesbury@gmail.com

@colesbury @miss-islington
pythongh-121652: Handle allocate_weakref returning NULL (pythonGH-1…
8526cc4 
…21653)

The `allocate_weakref` may return NULL when out of memory. We need to
handle that case and propagate the error.
(cherry picked from commit a640a60)

Co-authored-by: Sam Gross <colesbury@gmail.com>
This was referenced Jul 13, 2024
Closed
Merged
@colesbury colesbury enabled auto-merge (squash) July 13, 2024 16:09
@colesbury colesbury merged commit f78e1aa into python:3.13 Jul 13, 2024
34 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
skip news
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@miss-islington @colesbury