DM-21314: Investigate GC problems with Storable #75
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.
This PR adds a custom holder type that blocks Python garbage collection of the associated object for the lifetime of the holder. It must be used for any class that supports Python subclasses.
Despite my best efforts, I only partially understand how
PySharedPtr
works. In particular, while I know that all C++ classes with direct Python subclasses need to usePySharedPtr
as their holder type, I'm not sure if the same goes for their superclasses, or whether that depends on, e.g., the static types used in function signatures.