PyWeakref_GetObject removed in Python 3.15#2729
Merged
Avasam merged 1 commit intomhammond:mainfrom Apr 13, 2026
Merged
Conversation
PyWeakref_GetObject removed in 3.15
7 tasks
2af8b19 to
5b9c7d0
Compare
5b9c7d0 to
f5f85ad
Compare
PyWeakref_GetObject removed in 3.15PyWeakref_GetObject removed in Python 3.15
Collaborator
|
Looks good to me. |
mhammond
approved these changes
Apr 12, 2026
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
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.
Addresses a 3.15 Python C API Removal listed in #2588
My understanding is that
PyWeakref_GetRefcreates and sets a strong reference that needs to be handled explicitly.There's a comment alluding that this could maybe be handled differently, but I'm just trying to get the build and tests passing:
pywin32/Pythonwin/win32assoc.h
Lines 31 to 33 in 79096cd