-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-30654: Do not reset SIGINT handler to SIG_DFL in finisignal #7146
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@pitrou Now let's get this in before procedure changes again ;-) |
Ok, I'm gonna merge. I sincerely hope this doesn't cause any regression. |
…onGH-7146) (cherry picked from commit e905c84) Co-authored-by: pkerling <pkerling@casix.org>
GH-7306 is a backport of this pull request to the 3.7 branch. |
…onGH-7146) (cherry picked from commit e905c84) Co-authored-by: pkerling <pkerling@casix.org>
GH-7307 is a backport of this pull request to the 3.6 branch. |
@pitrou Thanks a lot! Glad this made it for 3.7. |
Sorry, @pkerling and @pitrou, I could not cleanly backport this to |
…pythonGH-7146). (cherry picked from commit e905c84)
…pythonGH-7146). (cherry picked from commit e905c84)
GH-7347 is a backport of this pull request to the 2.7 branch. |
Instead of saving old_siginthandler which will always be SIG_DFL, just use the normal reset code. This means that SIGINT will not be reset to SIG_DFL if it had a custom C handler during initialization, since
func
will bePy_None
then.I'm not sure if this is the intended behavior. But the prior behavior was broken, so it's an improvement.
https://bugs.python.org/issue30654
Supersedes #2162 (now for master branch)
https://bugs.python.org/issue30654