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 steve.dower
Recipients Chris Billington, eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-02-08.15:25:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1549639541.34.0.596034285094.issue35935@roundup.psfhosted.org>
In-reply-to
Content
I'm not sure it's quite as simple as calling sys.exit, but it would be a great project to bring universal cancellation support to all (regularly) blocking functions. Asyncio has suffered from this as well.

Part of the problem is that POSIX APIs often don't support cancellation, and so things have been designed in ways that prevent use of Windows's cancellation support (via APCs or kernel events). Given that we would have to emulate a lot of things on all platforms to make it consistent, this is certainly a PEP and long-term project. (And probably a lot of arguments with people who don't like new abstractions :( )

But on this particular issue, making the unconditional wait be interruptable by signals shouldn't be impossible. It's been done elsewhere, so probably just this one got missed.
History
Date User Action Args
2019-02-08 15:25:43steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, eryksun, Chris Billington
2019-02-08 15:25:41steve.dowersetmessageid: <1549639541.34.0.596034285094.issue35935@roundup.psfhosted.org>
2019-02-08 15:25:41steve.dowerlinkissue35935 messages
2019-02-08 15:25:40steve.dowercreate