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

gh-105766: Document that Custom Allocators Must Be Thread-Safe #107519

Merged
merged 3 commits into from
Jul 31, 2023

Conversation

ericsnowcurrently
Copy link
Member

@ericsnowcurrently ericsnowcurrently commented Jul 31, 2023

@ericsnowcurrently ericsnowcurrently enabled auto-merge (squash) July 31, 2023 23:06
@ericsnowcurrently ericsnowcurrently merged commit db361a3 into python:main Jul 31, 2023
@miss-islington
Copy link
Contributor

Thanks @ericsnowcurrently for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jul 31, 2023
@bedevere-bot
Copy link

GH-107522 is a backport of this pull request to the 3.12 branch.

@bedevere-bot bedevere-bot removed the needs backport to 3.12 bug and security fixes label Jul 31, 2023
@ericsnowcurrently ericsnowcurrently deleted the docs-allocators-gil branch July 31, 2023 23:12
ericsnowcurrently added a commit that referenced this pull request Jul 31, 2023
…gh-107519) (gh-107522)

gh-105766: Document that Custom Allocators Must Be Thread-Safe (gh-107519)
(cherry picked from commit db361a3)

Co-authored-by: Eric Snow <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir skip news
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants