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

[3.12] gh-100227: Lock Around Use of the Global "atexit" State (gh-105514) #105517

Merged
merged 2 commits into from
Jun 8, 2023

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Jun 8, 2023

The risk of a race with this state is relatively low, but we play it safe anyway.
(cherry picked from commit 7799c8e)

Co-authored-by: Eric Snow [email protected]

…gh-105514)

The risk of a race with this state is relatively low, but we play it safe anyway.
(cherry picked from commit 7799c8e)

Co-authored-by: Eric Snow <[email protected]>
Only internal ABI was changed.
@ericsnowcurrently ericsnowcurrently enabled auto-merge (squash) June 8, 2023 18:53
@ericsnowcurrently ericsnowcurrently merged commit 2ad2bd8 into python:3.12 Jun 8, 2023
@miss-islington miss-islington deleted the backport-7799c8e-3.12 branch June 8, 2023 19:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants