Skip to content

Conversation

@mpage
Copy link
Contributor

@mpagempage commented Mar 14, 2024

Since 3.12 allocating a GC-able object cannot trigger GC. This allows us to simplify the logic for creating the canonical callback-less proxy object.

Since 3.12 allocating a GC-able object cannot trigger GC. This allows us to simplify the logic for creating the canonical callback-less proxy object.
@mpage
Copy link
ContributorAuthor

The CIFuzz (memory) failure is unrelated to this PR. It's failing in the same way on other PRs and likely main.

@mpagempage requested a review from colesburyMarch 15, 2024 01:35
@mpagempage marked this pull request as ready for review March 15, 2024 01:36
@colesburycolesbury merged commit ce2c996 into python:mainMar 15, 2024
vstinner pushed a commit to vstinner/cpython that referenced this pull request Mar 20, 2024
Since 3.12, allocating a GC-able object cannot trigger GC. This allows us to simplify the logic for creating the canonical callback-less proxy object.
adorilson pushed a commit to adorilson/cpython that referenced this pull request Mar 25, 2024
Since 3.12, allocating a GC-able object cannot trigger GC. This allows us to simplify the logic for creating the canonical callback-less proxy object.
diegorusso pushed a commit to diegorusso/cpython that referenced this pull request Apr 17, 2024
Since 3.12, allocating a GC-able object cannot trigger GC. This allows us to simplify the logic for creating the canonical callback-less proxy object.
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@mpage@colesbury