Skip to content

[3.13] gh-144706: Warn against using synchronization primitives within signal handlers (GH-144736) #144768

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
ZeroIntensity merged 1 commit into from
Feb 12, 2026
Merged

[3.13] gh-144706: Warn against using synchronization primitives within signal handlers (GH-144736) #144768

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 5 additions & 0 deletions Doc/library/signal.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,6 +68,11 @@ the synchronization primitives from the :mod:`threading` module instead.

Besides, only the main thread of the main interpreter is allowed to set a new signal handler.

.. warning::

Synchronization primitives such as :class:`threading.Lock` should not be used
within signal handlers. Doing so can lead to unexpected deadlocks.


Module contents
---------------
Expand Down
Loading