fix(python): Ensure reference-counting tests are skipped on PyPy #453
Conversation
This file contains 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.
PyPy's garbage collector/object deletion is not as predictable as CPython's, so you can't be sure that when you run
gc.collect()that all unreferenced objects will be removed, and when youdelan object, basically nothing happens (except that future garbage collections might destroy it). I did check to make sure the deleters are actually running on pypy (usingbrew install pypy3.10) manually and added a wrapper around cibuildwheel such that one can check pypy locally when debugging one of these issues.