Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
gh-129165: Clarify that signal.raise_signal() sends signal to calling thread#129167
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
Emir2099 wants to merge3 commits intopython:mainChoose a base branch
base:main
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
+1 −1
Conversation
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
| @@ -397,7 +397,7 @@ The :mod:`signal` module defines the following functions: | |||
| .. function:: raise_signal(signum) | |||
| Sends a signal to the calling process. Returns nothing. | |||
| Sends a signal to the callingthread, not the entireprocess. Returns nothing. | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
- While we're here, it might be worth mentioning that on POSIX systems, this is equivalent to calling
signal.pthread_kill(threading.get_ident(), signum). Or, we could just link to themanpages forraise. - This is the correct description for POSIX, but what about Windows?
python-cla-botbot commentedApr 18, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
All commit authors signed the Contributor License Agreement. |
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
awaiting reviewdocsDocumentation in the Doc dir needs backport to 3.13bugs and security fixes needs backport to 3.14bugs and security fixes skip news
4 participants
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.
Uh oh!
There was an error while loading.Please reload this page.
The documentation for signal.raise_signal(signum) previously stated that it
"sends a signal to the calling process," which is misleading. In reality,
the signal is sent to the calling thread, which may cause different behavior
in multi-threaded applications.
This PR updates the documentation to clarify that
raise_signal()sendsthe signal to the calling thread instead of the entire process.
Fixesgh-129165.
📚 Documentation preview 📚:https://cpython-previews--129167.org.readthedocs.build/