Author asvetlov
Recipients Roland Netzsch, asvetlov, yselivanov
Date 2019-06-08.15:23:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560007435.8.0.490450106252.issue37202@roundup.psfhosted.org>
In-reply-to
Content
I don't follow what reliability guarantee are you requesting.

A cite from task.cancel() docstring:

> Request that this task cancel itself.

        This arranges for a CancelledError to be thrown into the
        wrapped coroutine on the next cycle through the event loop.
        The coroutine then has a chance to clean up or even deny
        the request using try/except/finally.

        Unlike Future.cancel, this does not guarantee that the
        task will be cancelled: the exception might be caught and
        acted upon, delaying cancellation of the task or preventing
        cancellation completely.  The task may also return a value or
        raise a different exception.

        Immediately after this method is called, Task.cancelled() will
        not return True (unless the task was already cancelled).  A
        task will be marked as cancelled when the wrapped coroutine
        terminates with a CancelledError exception (even if cancel()
        was not called).

task.cancelled() returns True for canceled and finished tasks, but task.cancel() is a request for cancellation. The requested task needs some time to gracefully finish itself.
History
Date User Action Args
2019-06-08 15:23:55asvetlovsetrecipients: + asvetlov, yselivanov, Roland Netzsch
2019-06-08 15:23:55asvetlovsetmessageid: <1560007435.8.0.490450106252.issue37202@roundup.psfhosted.org>
2019-06-08 15:23:55asvetlovlinkissue37202 messages
2019-06-08 15:23:55asvetlovcreate