]> granicus.if.org Git - python/commit
bpo-32751: Wait for task cancellation in asyncio.wait_for() (GH-7216)
authorElvis Pranskevichus <elvis@magic.io>
Tue, 29 May 2018 21:31:01 +0000 (17:31 -0400)
committerYury Selivanov <yury@magic.io>
Tue, 29 May 2018 21:31:01 +0000 (17:31 -0400)
commite2b340ab4196e1beb902327f503574b5d7369185
treed47d0236c55372324d406d99ae67b0cc14399c86
parent863b6749093a86810c4077112a857363410cc221
bpo-32751: Wait for task cancellation in asyncio.wait_for() (GH-7216)

Currently, asyncio.wait_for(fut), upon reaching the timeout deadline,
cancels the future and returns immediately.  This is problematic for
when *fut* is a Task, because it will be left running for an arbitrary
amount of time.  This behavior is iself surprising and may lead to
related bugs such as the one described in bpo-33638:

    condition = asyncio.Condition()
    async with condition:
        await asyncio.wait_for(condition.wait(), timeout=0.5)

Currently, instead of raising a TimeoutError, the above code will fail
with `RuntimeError: cannot wait on un-acquired lock`, because
`__aexit__` is reached _before_ `condition.wait()` finishes its
cancellation and re-acquires the condition lock.

To resolve this, make `wait_for` await for the task cancellation.
The tradeoff here is that the `timeout` promise may be broken if the
task decides to handle its cancellation in a slow way.  This represents
a behavior change and should probably not be back-patched to 3.6 and
earlier.
Doc/library/asyncio-task.rst
Lib/asyncio/tasks.py
Lib/test/test_asyncio/test_locks.py
Lib/test/test_asyncio/test_tasks.py
Misc/NEWS.d/next/Library/2018-05-29-15-32-18.bpo-32751.oBTqr7.rst [new file with mode: 0644]