[3.7] bpo-34872: Fix self-cancellation in C implementation of asyncio.Task (GH-9679) (GH-9691)
The C implementation of asyncio.Task currently fails to perform the
cancellation cleanup correctly in the following scenario.
async def task1():
async def task2():
await task3 # task3 is never cancelled
asyncio.current_task().cancel()
await asyncio.create_task(task2())
The actuall error is a hardcoded call to `future_cancel()` instead of
calling the `cancel()` method of a future-like object.
Thanks to Vladimir Matveev for noticing the code discrepancy and to
Yury Selivanov for coming up with a pathological scenario..
(cherry picked from commit 548ce9dedd2e90945970671d441436a6a91608ab)
Co-authored-by: Elvis Pranskevichus <elvis@magic.io>
https://bugs.python.org/issue34872
diff --git a/Modules/_asynciomodule.c b/Modules/_asynciomodule.c
index 0c161fb..9f7500a 100644
--- a/Modules/_asynciomodule.c
+++ b/Modules/_asynciomodule.c
@@ -2662,14 +2662,19 @@
if (task->task_must_cancel) {
PyObject *r;
- r = future_cancel(fut);
+ int is_true;
+ r = _PyObject_CallMethodId(fut, &PyId_cancel, NULL);
if (r == NULL) {
return NULL;
}
- if (r == Py_True) {
+ is_true = PyObject_IsTrue(r);
+ Py_DECREF(r);
+ if (is_true < 0) {
+ return NULL;
+ }
+ else if (is_true) {
task->task_must_cancel = 0;
}
- Py_DECREF(r);
}
Py_RETURN_NONE;