-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
bpo-30654: Do not reset SIGINT handler to SIG_DFL in finisignal #2162
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
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. Thanks again to your contribution and we look forward to looking at it! |
Thank you @pkerling for submitting this patch. The fix looks sane to me. |
Tried to add a NEWS entry. |
Hi, what's the status? Do I still need to do something? This is a small fix and it's sitting here for quite some time now. |
Friendly ping :-) |
Hi @pkerling I'm sorry for letting this slip. In turn there are two issues:
|
Superseded by #7146 |
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