[3.15] gh-154139: Document that curses is not thread-safe (GH-154173) - #155690
Open
serhiy-storchaka wants to merge 1 commit into
Open
[3.15] gh-154139: Document that curses is not thread-safe (GH-154173)#155690serhiy-storchaka wants to merge 1 commit into
serhiy-storchaka wants to merge 1 commit into
Conversation
…onGH-154173) Whether curses is thread-safe depends on the library and how it was built. The blocking and refresh methods release the GIL, so with a non-reentrant curses, unsynchronized use from several threads can crash. The reference to window.use() and screen.use() is omitted: they were added in 3.16. (cherry picked from commit 1ed6b78) Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Documentation build overview
296 files changed ·
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Whether curses is thread-safe depends on the library and how it was built.
The blocking and refresh methods release the GIL, so with a non-reentrant curses, unsynchronized use from several threads can crash.
The reference to
window.use()andscreen.use()is omitted: they were added in 3.16.(cherry picked from commit 1ed6b78)
🤖 Generated with Claude Code