8000 gh-105766: Document that Custom Allocators Must Be Thread-Safe by ericsnowcurrently · Pull Request #107519 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content
8000

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

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Jul 31, 2023
Merged

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

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e6d16ca
Document that custom allocators must be thread-safe.
ericsnowcurrently Jul 31, 2023
c268cf2
Add a What's New entry.
ericsnowcurrently Jul 31, 2023
c2c7735
Fix a typo.
ericsnowcurrently Jul 31, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Fix a typo.
  • Loading branch information
@ericsnowcurrently
ericsnowcurrently committed Jul 31, 2023
commit c2c7735e388e87db665caec9fd0325e0e6d2a72e
2 changes: 1 addition & 1 deletion Doc/whatsnew/3.12.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1881,7 +1881,7 @@ Porting to Python 3.12
that don't have their own state, including "hooks", are not affected.
If your custom allocator is not already thread-safe and you need
guidance then please create a new GitHub issue
and CC `@ericsnowcurrently`.
and CC ``@ericsnowcurrently``.

Deprecated
----------
Expand Down
0