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 davin, pitrou, rhettinger, sbt, vstinner
Date 2017-04-27.11:32:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1493292750.25.0.385497851554.issue30185@psf.upfronthosting.co.za>
In-reply-to
Content
> A simpler solution would actually be to catch KeyboardInterrupt inside the forkserver loop and exit cleanly...

I'm not sure that we always want to exit on CTRL-c. But I agree that the forkserver has to handle CTRL-c. Maybe ignore it, but be killed when its master gets a CTRL-c?
History
Date User Action Args
2017-04-27 11:32:30vstinnersetrecipients: + vstinner, rhettinger, pitrou, sbt, davin
2017-04-27 11:32:30vstinnersetmessageid: <1493292750.25.0.385497851554.issue30185@psf.upfronthosting.co.za>
2017-04-27 11:32:30vstinnerlinkissue30185 messages
2017-04-27 11:32:30vstinnercreate