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

2019-06-08 Thread Roland Netzsch
Change by Roland Netzsch : -- resolution: -> not a bug ___ Python tracker <https://bugs.python.org/issue37202> ___ ___ Python-bugs-list mailing list Un

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

2019-06-08 Thread Roland Netzsch
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 <https://bugs.python.org/issue37

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

2019-06-08 Thread Roland Netzsch
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 <ht

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

2019-06-08 Thread Roland Netzsch
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