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 njs
Recipients asvetlov, bar.harel, njs, yselivanov
Date 2018-02-14.10:21:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1518603680.31.0.467229070634.issue32841@psf.upfronthosting.co.za>
In-reply-to
Content
> Having shield not cancel immediately but rather wait and cancel will cause long timed shielded operations to stall the task cancellation, usually for no good. This isn't the general case.

What I'm suggesting is that maybe it actually is good in the general case :-). If an operation can't be cancelled, that's too bad, but it's generally still better to wait then to silently leak it into the background.
History
Date User Action Args
2018-02-14 10:21:20njssetrecipients: + njs, asvetlov, yselivanov, bar.harel
2018-02-14 10:21:20njssetmessageid: <1518603680.31.0.467229070634.issue32841@psf.upfronthosting.co.za>
2018-02-14 10:21:20njslinkissue32841 messages
2018-02-14 10:21:20njscreate