Guido van Rossum <[email protected]> added the comment:
Hm, I see. So the problem is that in the interval between move_on's calls to
t.cancel() and t.uncancel(), if the web server calls t.cancel() that will just
return False. So the web server would have to implement some other mechanism
for cancelling operations.
That's indeed unfortunate. Maybe we should just roll back that aspect of the
TaskGroup PR -- in particular, remove these two lines:
if self._cancel_requested:
return False
from Task.cancel(). These lines don't matter for TaskGroup (it works without
them), and they weren't there before yesterday, so the fallout would be very
localized.
@asvetlov What do you think?
----------
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue46771>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
