Nathaniel Smith <n...@pobox.com> added the comment:
> 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.
resolution: fixed ->
stage: resolved -> patch review
status: closed -> open
Python tracker <rep...@bugs.python.org>
Python-bugs-list mailing list