]> git.ipfire.org Git - thirdparty/Python/cpython.git/commit
[3.6] bpo-34872: Fix self-cancellation in C implementation of asyncio.Task (GH-9679...
authorElvis Pranskevichus <elvis@magic.io>
Wed, 3 Oct 2018 15:28:44 +0000 (11:28 -0400)
committerMiss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Wed, 3 Oct 2018 15:28:44 +0000 (08:28 -0700)
commit166773df0ce6c852130f524029fa2e62b37b89cb
tree7b8928090dcd7dfc06e21cb51728e19a72a50ee3
parent6580e52b64cb207f03a1bf86a18f088b081c10f4
[3.6] bpo-34872: Fix self-cancellation in C implementation of asyncio.Task (GH-9679) (GH-9690)

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)

https://bugs.python.org/issue34872
Lib/test/test_asyncio/test_tasks.py
Misc/NEWS.d/next/Library/2018-10-02-19-36-34.bpo-34872.yWZRhI.rst [new file with mode: 0644]
Modules/_asynciomodule.c