Skip to content

[3.15] gh-154139: Document that curses is not thread-safe (GH-154173) - #155690

Merged
hugovk merged 1 commit into
python:3.15from
serhiy-storchaka:backport-1ed6b78-3.15
Aug 27, 2026
Merged

[3.15] gh-154139: Document that curses is not thread-safe (GH-154173)#155690
hugovk merged 1 commit into
python:3.15from
serhiy-storchaka:backport-1ed6b78-3.15

Conversation

@serhiy-storchaka

@serhiy-storchaka serhiy-storchaka commented Aug 13, 2026

Copy link
Copy Markdown
Member

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)

🤖 Generated with Claude Code

…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>
@read-the-docs-community

Copy link
Copy Markdown

@hugovk
hugovk merged commit 4951a11 into python:3.15 Aug 27, 2026
43 checks passed
@github-project-automation github-project-automation Bot moved this from Todo to Done in Docs PRs Aug 27, 2026
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

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants