This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients ned.deily, pitrou, pkerling, vstinner
Date 2018-06-01.10:08:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> You have it backwards.  Please read the bug report.

I'm confused by the NEWS entry:

+Fixed reset of the SIGINT handler to SIG_DFL on interpreter shutdown even
+when there was a custom handler set previously. Patch by Philipp Kerling.

I read it as Python now always reset SIGINT to SIG_DFL. The commit title is more explicit: "Do not reset SIGINT (...)".

I propose to rephrase the NEWS entry as:

Fix signal handlers when Python is embedded. On Python shutdown, do not reset the SIGINT handler to SIG_DFL, when a custom handler has been set before Python initialization. Patch by Philipp Kerling.


Ok, now I understood the change. In this case, I'm ok to backport it to 3.6 and 3.7.

Python 2.7 has this behavior since 10 years, it seems like people learnt to live with it. I also dislike touching Python 2.7, to prevent any risk of regression if someone really rely on the current behavior.
Date User Action Args
2018-06-01 10:08:56vstinnersetrecipients: + vstinner, pitrou, ned.deily, pkerling
2018-06-01 10:08:56vstinnersetmessageid: <>
2018-06-01 10:08:56vstinnerlinkissue30654 messages
2018-06-01 10:08:56vstinnercreate