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 pitrou
Recipients davin, pitrou, rhettinger, sbt, vstinner
Date 2017-04-27.11:39:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I'm not sure that we always want to exit on CTRL-c.

That's what the forkserver does right now, it's just that it does it with a traceback that's useless to the user.

> Maybe ignore it, but be killed when its master gets a CTRL-c?

That's a possibility (the forkserver should already exit automatically when its parent dies), the problem is what to do for the forkserver's children?  Should they restore the default signal handler?

Simply silencing the KeyboardInterrupt traceback at least is a straightforward solution with little risk of side effects.
Date User Action Args
2017-04-27 11:39:37pitrousetrecipients: + pitrou, rhettinger, vstinner, sbt, davin
2017-04-27 11:39:37pitrousetmessageid: <>
2017-04-27 11:39:37pitroulinkissue30185 messages
2017-04-27 11:39:37pitroucreate