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 gregory.p.smith
Recipients SamB, eryksun, foom, gregory.p.smith, jwilk, loewis, martin.panter, mwh, petri.lehtinen, pitrou, rnk, vstinner
Date 2019-02-16.21:08:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550351283.49.0.963847848115.issue1054041@roundup.psfhosted.org>
In-reply-to
Content
This is in for 3.8.

On earlier or unpatched Python versions: application owners have a workaround f they do not mind skipping a clean application shutdown (destructors) on posix platforms:
catch KeyboardInterrupt, reset SIGINT to SIG_DFL, kill(getpid(), SIGINT).  If you somehow need the python destructor cleanup (never guaranteed, so unwise to _depend_ on it) you could do that in a C atexit handler.

On Windows the workaround is easier without altering clean shutdown, catch KeyboardInterrupt and sys.exit(0xC000013A - 2**32).
History
Date User Action Args
2019-02-16 21:08:03gregory.p.smithsetrecipients: + gregory.p.smith, mwh, loewis, foom, pitrou, vstinner, jwilk, rnk, petri.lehtinen, martin.panter, SamB, eryksun
2019-02-16 21:08:03gregory.p.smithsetmessageid: <1550351283.49.0.963847848115.issue1054041@roundup.psfhosted.org>
2019-02-16 21:08:03gregory.p.smithlinkissue1054041 messages
2019-02-16 21:08:03gregory.p.smithcreate