Skip to content
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.

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

test with python 3.13 #446

Merged
merged 2 commits into from May 11, 2024
Merged

test with python 3.13 #446

merged 2 commits into from May 11, 2024

Conversation

davidism
Copy link
Member

No description provided.

@davidism
Copy link
Member Author

As discussed in #445, I don't understand exactly how the leak test is working. It's not clear why we expect the GC object count to be the same every loop, as we don't know what else is going on in Python internals. JITs seems to mess with this count, as does calling gc.collect(). They seem to stabilize at 2 instead of 1 unique count. Presumably a real leak would result in many different counts.

@davidism davidism merged commit 53d7cb7 into main May 11, 2024
12 checks passed
@davidism davidism deleted the 313 branch May 11, 2024 20:17
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 26, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant