[issue37202] Future.cancelled is not set to true immediately after calling Future.cancel

Change by Andrew Svetlov : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue37202] Future.cancelled is not set to true immediately after calling Future.cancel

Change by Roland Netzsch : -- resolution: -> not a bug ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37202] Future.cancelled is not set to true immediately after calling Future.cancel

Andrew Svetlov added the comment: 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

[issue37202] Future.cancelled is not set to true immediately after calling Future.cancel

Roland Netzsch added the comment: So there is no way to reliably find out whether a task has been cancelled by calling Task.cancelled()? -- ___ Python tracker ___

[issue37202] Future.cancelled is not set to true immediately after calling Future.cancel

Andrew Svetlov added the comment: This is the expected behavior. asyncio.ensure_future() returns not a future but a task for your case. Task cancellation requires at least one context switch to finish the task. P.S. I suggest replacing `asyncio.ensure_future()` with `asyncio.create_task()`

[issue37202] Future.cancelled is not set to true immediately after calling Future.cancel

Roland Netzsch added the comment: Python-Version: [stuxcrystal@caprica ~]$ python3.7 --version Python 3.7.3 Additional Notes: Distribution: Fedora 30 (Workstation Edition) Kernel: x86_64 Linux 5.0.9-301.fc30.x86_64 -- ___ Python tracker

[issue37202] Future.cancelled is not set to true immediately after calling Future.cancel

New submission from Roland Netzsch : The attached file produces the following output: wait is still running wait is not set to cancelled! Awaiting cancelled future produced a CancelledError. A look a the documentation does not suggest a need to await the future in order to make