协程和任务

此节提纲的高级 asyncio API 能操控协程和任务。

协程

协程 declared with the async/await syntax is the preferred way of writing asyncio applications. For example, the following snippet of code (requires Python 3.7+) prints “hello”, waits 1 second, and then prints “world”:

>>> import asyncio
>>> async def main():
...     print('hello')
...     await asyncio.sleep(1)
...     print('world')
>>> asyncio.run(main())
hello
world
						

注意,简单调用协程不会调度它的执行:

>>> main()
<coroutine object main at 0x1053bb7c8>
						

To actually run a coroutine, asyncio provides three main mechanisms:

  • The asyncio.run() 函数运行顶层入口点 main() 函数 (见以上范例)。

  • 等待协程。以下代码片段将在等待 1 秒后打印 hello,然后打印 world 后于等待 another 2 秒:

    import asyncio
    import time
    async def say_after(delay, what):
        await asyncio.sleep(delay)
        print(what)
    async def main():
        print(f"started at {time.strftime('%X')}")
        await say_after(1, 'hello')
        await say_after(2, 'world')
        print(f"finished at {time.strftime('%X')}")
    asyncio.run(main())
    								

    期望输出:

    started at 17:13:52
    hello
    world
    finished at 17:13:55
    								
  • The asyncio.create_task() 函数并发运行协程如 asyncio Tasks .

    让我们修改以上范例并运行 2 say_after 协程 concurrently :

    async def main():
        task1 = asyncio.create_task(
            say_after(1, 'hello'))
        task2 = asyncio.create_task(
            say_after(2, 'world'))
        print(f"started at {time.strftime('%X')}")
        # Wait until both tasks are completed (should take
        # around 2 seconds.)
        await task1
        await task2
        print(f"finished at {time.strftime('%X')}")
    								

    注意,现在期望的输出展示片段运行速度比之前快了 1 秒:

    started at 17:14:32
    hello
    world
    finished at 17:14:34
    								

可期待

我们说对象是 awaitable object if it can be used in an await expression. Many asyncio APIs are designed to accept awaitables.

有 3 种主要类型的 awaitable 对象: 协程 , 任务 ,和 未来 .

协程

Python 协程是 awaitables 因此可以从其它协程等待:

import asyncio
async def nested():
    return 42
async def main():
    # Nothing happens if we just call "nested()".
    # A coroutine object is created but not awaited,
    # so it *won't run at all*.
    nested()
    # Let's do it differently now and await it:
    print(await nested())  # will print "42".
asyncio.run(main())
						

重要

In this documentation the term “coroutine” can be used for two closely related concepts:

  • a 协程函数 async def 函数;

  • a 协程对象 : an object returned by calling a 协程函数 .

asyncio also supports legacy generator-based 协程。

任务

任务 被用于调度协程 concurrently .

When a coroutine is wrapped into a Task with functions like asyncio.create_task() the coroutine is automatically scheduled to run soon:

import asyncio
async def nested():
    return 42
async def main():
    # Schedule nested() to run soon concurrently
    # with "main()".
    task = asyncio.create_task(nested())
    # "task" can now be used to cancel "nested()", or
    # can simply be awaited to wait until it is complete:
    await task
asyncio.run(main())
						

未来

A Future is a special 低级 awaitable object that represents an eventual result of an asynchronous operation.

When a Future object is awaited it means that the coroutine will wait until the Future is resolved in some other place.

Future objects in asyncio are needed to allow callback-based code to be used with async/await.

Normally there is no need to create Future objects at the application level code.

Future objects, sometimes exposed by libraries and some asyncio APIs, can be awaited:

async def main():
    await function_that_returns_a_future_object()
    # this is also valid:
    await asyncio.gather(
        function_that_returns_a_future_object(),
        some_python_coroutine()
    )
					

A good example of a low-level function that returns a Future object is loop.run_in_executor() .

运行异步程序

asyncio. run ( coro , * , debug=False )

执行 协程 coro 并返回结果。

This function runs the passed coroutine, taking care of managing the asyncio event loop and 定稿异步生成器 .

无法调用此函数,当另一 asyncio 事件循环在同一线程中运行时。

debug is True ,以调试模式运行事件循环。

此函数总是创建新事件循环,并在结束时关闭它。它应被用作 asyncio 程序的主入口点,且理想情况下只应被调用一次。

范例:

async def main():
    await asyncio.sleep(1)
    print('hello')
asyncio.run(main())
						

3.7 版新增。

注意

The source code for asyncio.run() 可以找到在 Lib/asyncio/runners.py .

创建任务

asyncio. create_task ( coro , * , name=None )

包裹 coro 协程 Task 并调度其执行。返回任务对象。

name 不是 None ,将它设为任务名称使用 Task.set_name() .

在循环中执行的任务的返回通过 get_running_loop() , RuntimeError 被引发若当前线程中没有正运行的循环。

This function has been added in Python 3.7 . Prior to Python 3.7, the low-level asyncio.ensure_future() function can be used instead:

async def coro():
    ...
# In Python 3.7+
task = asyncio.create_task(coro())
...
# This works in all Python versions but is less readable
task = asyncio.ensure_future(coro())
...
						

3.7 版新增。

3.8 版改变: 添加 name 参数。

休眠

协程 asyncio. sleep ( delay , result=None , * , loop=None )

阻塞 delay 秒。

result 有提供,将它返回给调用者当协程完成时。

sleep() 始终挂起当前任务,允许其它任务运行。

从 3.8 版起弃用,将在 3.10 版中移除: The loop 参数。

在 5 秒内每秒显示当前日期的协程范例:

import asyncio
import datetime
async def display_date():
    loop = asyncio.get_running_loop()
    end_time = loop.time() + 5.0
    while True:
        print(datetime.datetime.now())
        if (loop.time() + 1.0) >= end_time:
            break
        await asyncio.sleep(1)
asyncio.run(display_date())
						

并发运行任务

awaitable asyncio. gather ( *aws , loop=None , return_exceptions=False )

运行 可期待对象 aws sequence concurrently .

若任何可期待在 aws 是协程,自动作为 Task (任务) 被调度。

If all awaitables are completed successfully, the result is an aggregate list of returned values. The order of result values corresponds to the order of awaitables in aws .

return_exceptions is False (default), the first raised exception is immediately propagated to the task that awaits on gather() . Other awaitables in the aws sequence won’t be cancelled and will continue to run.

return_exceptions is True , exceptions are treated the same as successful results, and aggregated in the result list.

gather() is cancelled , all submitted awaitables (that have not completed yet) are also cancelled .

If any Task or Future from the aws sequence is cancelled , it is treated as if it raised CancelledError – the gather() call is not cancelled in this case. This is to prevent the cancellation of one submitted Task/Future to cause other Tasks/Futures to be cancelled.

从 3.8 版起弃用,将在 3.10 版中移除: The loop 参数。

范例:

import asyncio
async def factorial(name, number):
    f = 1
    for i in range(2, number + 1):
        print(f"Task {name}: Compute factorial({i})...")
        await asyncio.sleep(1)
        f *= i
    print(f"Task {name}: factorial({number}) = {f}")
async def main():
    # Schedule three calls *concurrently*:
    await asyncio.gather(
        factorial("A", 2),
        factorial("B", 3),
        factorial("C", 4),
    )
asyncio.run(main())
# Expected output:
#
#     Task A: Compute factorial(2)...
#     Task B: Compute factorial(2)...
#     Task C: Compute factorial(2)...
#     Task A: factorial(2) = 2
#     Task B: Compute factorial(3)...
#     Task C: Compute factorial(3)...
#     Task B: factorial(3) = 6
#     Task C: Compute factorial(4)...
#     Task C: factorial(4) = 24
						

注意

return_exceptions is False, cancelling gather() after it has been marked done won’t cancel any submitted awaitables. For instance, gather can be marked done after propagating an exception to the caller, therefore, calling gather.cancel() after catching an exception (raised by one of the awaitables) from gather won’t cancel any other awaitables.

3.7 版改变: gather itself is cancelled, the cancellation is propagated regardless of return_exceptions .

从消除屏蔽

awaitable asyncio. shield ( aw , * , loop=None )

Protect an awaitable object from being cancelled .

aw 是协程,自动作为 Task (任务) 被调度。

语句:

res = await shield(something())
						

相当于:

res = await something()
						

except that if the coroutine containing it is cancelled, the Task running in something() is not cancelled. From the point of view of something() , the cancellation did not happen. Although its caller is still cancelled, so the “await” expression still raises a CancelledError .

something() is cancelled by other means (i.e. from within itself) that would also cancel shield() .

If it is desired to completely ignore cancellation (not recommended) the shield() function should be combined with a try/except clause, as follows:

try:
    res = await shield(something())
except CancelledError:
    res = None
						

从 3.8 版起弃用,将在 3.10 版中移除: The loop 参数。

超时

协程 asyncio. wait_for ( aw , timeout , * , loop=None )

等待 aw awaitable 完成采用超时。

aw 是协程,自动作为 Task (任务) 被调度。

timeout 可以是 None or a float or int number of seconds to wait for. If timeout is None , block until the future completes.

If a timeout occurs, it cancels the task and raises asyncio.TimeoutError .

要避免任务 cancellation ,将它包裹在 shield() .

The function will wait until the future is actually cancelled, so the total wait time may exceed the timeout .

If the wait is cancelled, the future aw is also cancelled.

从 3.8 版起弃用,将在 3.10 版中移除: The loop 参数。

范例:

async def eternity():
    # Sleep for one hour
    await asyncio.sleep(3600)
    print('yay!')
async def main():
    # Wait for at most 1 second
    try:
        await asyncio.wait_for(eternity(), timeout=1.0)
    except asyncio.TimeoutError:
        print('timeout!')
asyncio.run(main())
# Expected output:
#
#     timeout!
						

3.7 版改变: aw is cancelled due to a timeout, wait_for waits for aw to be cancelled. Previously, it raised asyncio.TimeoutError 立即。

等待原语

协程 asyncio. wait ( aws , * , loop=None , timeout=None , return_when=ALL_COMPLETED )

运行 可期待对象 aws iterable concurrently and block until the condition specified by return_when .

Returns two sets of Tasks/Futures: (done, pending) .

用法:

done, pending = await asyncio.wait(aws)
					

timeout (a float or int), if specified, can be used to control the maximum number of seconds to wait before returning.

Note that this function does not raise asyncio.TimeoutError . Futures or Tasks that aren’t done when the timeout occurs are simply returned in the second set.

return_when indicates when this function should return. It must be one of the following constants:

常量 描述
FIRST_COMPLETED The function will return when any future finishes or is cancelled.
FIRST_EXCEPTION The function will return when any future finishes by raising an exception. If no future raises an exception then it is equivalent to ALL_COMPLETED .
ALL_COMPLETED The function will return when all futures finish or are cancelled.

不像 wait_for() , wait() does not cancel the futures when a timeout occurs.

从 3.8 版起弃用: 若任何可期待在 aws is a coroutine, it is automatically scheduled as a Task. Passing coroutines objects to wait() directly is deprecated as it leads to confusing behavior .

从 3.8 版起弃用,将在 3.10 版中移除: The loop 参数。

注意

wait() schedules coroutines as Tasks automatically and later returns those implicitly created Task objects in (done, pending) sets. Therefore the following code won’t work as expected:

async def foo():
    return 42
coro = foo()
done, pending = await asyncio.wait({coro})
if coro in done:
    # This branch will never be run!
					

Here is how the above snippet can be fixed:

async def foo():
    return 42
task = asyncio.create_task(foo())
done, pending = await asyncio.wait({task})
if task in done:
    # Everything will work as expected now.
					

从 3.8 版起弃用: 将协程对象传递给 wait() directly is deprecated.

asyncio. as_completed ( aws , * , loop=None , timeout=None )

运行 可期待对象 aws iterable concurrently. Return an iterator of coroutines. Each coroutine returned can be awaited to get the earliest next result from the iterable of the remaining awaitables.

引发 asyncio.TimeoutError if the timeout occurs before all Futures are done.

从 3.8 版起弃用,将在 3.10 版中移除: The loop 参数。

范例:

for coro in as_completed(aws):
    earliest_result = await coro
    # ...
						

从其它线程调度

asyncio. run_coroutine_threadsafe ( coro , loop )

将协程提交给给定事件循环。是线程安全的。

返回 concurrent.futures.Future to wait for the result from another OS thread.

This function is meant to be called from a different OS thread than the one where the event loop is running. Example:

# Create a coroutine
coro = asyncio.sleep(1, result=3)
# Submit the coroutine to a given loop
future = asyncio.run_coroutine_threadsafe(coro, loop)
# Wait for the result with an optional timeout argument
assert future.result(timeout) == 3
						

If an exception is raised in the coroutine, the returned Future will be notified. It can also be used to cancel the task in the event loop:

try:
    result = future.result(timeout)
except asyncio.TimeoutError:
    print('The coroutine took too long, cancelling the task...')
    future.cancel()
except Exception as exc:
    print(f'The coroutine raised an exception: {exc!r}')
else:
    print(f'The coroutine returned: {result!r}')
						

并发和多线程 章节的文档编制。

Unlike other asyncio functions this function requires the loop argument to be passed explicitly.

3.5.1 版新增。

自省

asyncio. current_task ( loop=None )

返回目前正运行的 Task 实例,或 None 若没有任务在运行。

loop is None get_running_loop() 用于获取当前循环。

3.7 版新增。

asyncio. all_tasks ( loop=None )

Return a set of not yet finished Task objects run by the loop.

loop is None , get_running_loop() is used for getting current loop.

3.7 版新增。

任务对象

class asyncio. Task ( coro , * , loop=None , name=None )

A Future-like 对象运行 Python 协程 。不是线程安全的。

Tasks are used to run coroutines in event loops. If a coroutine awaits on a Future, the Task suspends the execution of the coroutine and waits for the completion of the Future. When the Future is done , the execution of the wrapped coroutine resumes.

Event loops use cooperative scheduling: an event loop runs one Task at a time. While a Task awaits for the completion of a Future, the event loop runs other Tasks, callbacks, or performs IO operations.

Use the high-level asyncio.create_task() function to create Tasks, or the low-level loop.create_task() or ensure_future() functions. Manual instantiation of Tasks is discouraged.

To cancel a running Task use the cancel() method. Calling it will cause the Task to throw a CancelledError exception into the wrapped coroutine. If a coroutine is awaiting on a Future object during cancellation, the Future object will be cancelled.

cancelled() can be used to check if the Task was cancelled. The method returns True if the wrapped coroutine did not suppress the CancelledError exception and was actually cancelled.

asyncio.Task 继承自 Future all of its APIs except Future.set_result() and Future.set_exception() .

Tasks support the contextvars module. When a Task is created it copies the current context and later runs its coroutine in the copied context.

3.7 版改变: 添加支持 contextvars 模块。

3.8 版改变: 添加 name 参数。

从 3.8 版起弃用,将在 3.10 版中移除: The loop 参数。

cancel ( )

Request the Task to be cancelled.

This arranges for a CancelledError exception to be thrown into the wrapped coroutine on the next cycle of the event loop.

The coroutine then has a chance to clean up or even deny the request by suppressing the exception with a try … … except CancelledError finally block. Therefore, unlike Future.cancel() , Task.cancel() does not guarantee that the Task will be cancelled, although suppressing cancellation completely is not common and is actively discouraged.

The following example illustrates how coroutines can intercept the cancellation request:

async def cancel_me():
    print('cancel_me(): before sleep')
    try:
        # Wait for 1 hour
        await asyncio.sleep(3600)
    except asyncio.CancelledError:
        print('cancel_me(): cancel sleep')
        raise
    finally:
        print('cancel_me(): after sleep')
async def main():
    # Create a "cancel_me" Task
    task = asyncio.create_task(cancel_me())
    # Wait for 1 second
    await asyncio.sleep(1)
    task.cancel()
    try:
        await task
    except asyncio.CancelledError:
        print("main(): cancel_me is cancelled now")
asyncio.run(main())
# Expected output:
#
#     cancel_me(): before sleep
#     cancel_me(): cancel sleep
#     cancel_me(): after sleep
#     main(): cancel_me is cancelled now
						
cancelled ( )

返回 True 若 Task cancelled .

The Task is cancelled when the cancellation was requested with cancel() and the wrapped coroutine propagated the CancelledError exception thrown into it.

done ( )

返回 True 若 Task done .

A Task is done when the wrapped coroutine either returned a value, raised an exception, or the Task was cancelled.

result ( )

Return the result of the Task.

If the Task is done , the result of the wrapped coroutine is returned (or if the coroutine raised an exception, that exception is re-raised.)

If the Task has been cancelled , this method raises a CancelledError 异常。

If the Task’s result isn’t yet available, this method raises a InvalidStateError 异常。

exception ( )

Return the exception of the Task.

If the wrapped coroutine raised an exception that exception is returned. If the wrapped coroutine returned normally this method returns None .

If the Task has been cancelled , this method raises a CancelledError 异常。

If the Task isn’t done yet, this method raises an InvalidStateError 异常。

add_done_callback ( callback , * , context=None )

Add a callback to be run when the Task is done .

This method should only be used in low-level callback-based code.

见文档编制为 Future.add_done_callback() 了解更多细节。

remove_done_callback ( callback )

移除 callback 从回调列表。

This method should only be used in low-level callback-based code.

见文档编制为 Future.remove_done_callback() 了解更多细节。

get_stack ( * , limit=None )

Return the list of stack frames for this Task.

If the wrapped coroutine is not done, this returns the stack where it is suspended. If the coroutine has completed successfully or was cancelled, this returns an empty list. If the coroutine was terminated by an exception, this returns the list of traceback frames.

The frames are always ordered from oldest to newest.

Only one stack frame is returned for a suspended coroutine.

可选 limit argument sets the maximum number of frames to return; by default all available frames are returned. The ordering of the returned list differs depending on whether a stack or a traceback is returned: the newest frames of a stack are returned, but the oldest frames of a traceback are returned. (This matches the behavior of the traceback module.)

print_stack ( * , limit=None , file=None )

Print the stack or traceback for this Task.

This produces output similar to that of the traceback module for the frames retrieved by get_stack() .

The limit 自变量会被传递给 get_stack() 直接。

The file argument is an I/O stream to which the output is written; by default output is written to sys.stderr .

get_coro ( )

Return the coroutine object wrapped by the Task .

3.8 版新增。

get_name ( )

Return the name of the Task.

If no name has been explicitly assigned to the Task, the default asyncio Task implementation generates a default name during instantiation.

3.8 版新增。

set_name ( value )

Set the name of the Task.

The value argument can be any object, which is then converted to a string.

In the default Task implementation, the name will be visible in the repr() output of a task object.

3.8 版新增。

classmethod all_tasks ( loop=None )

Return a set of all tasks for an event loop.

By default all tasks for the current event loop are returned. If loop is None get_event_loop() function is used to get the current loop.

Deprecated since version 3.7, will be removed in version 3.9: Do not call this as a task method. Use the asyncio.all_tasks() function instead.

classmethod current_task ( loop=None )

Return the currently running task or None .

loop is None get_event_loop() function is used to get the current loop.

Deprecated since version 3.7, will be removed in version 3.9: Do not call this as a task method. Use the asyncio.current_task() function instead.

基于生成器的协程

注意

Support for generator-based coroutines is 弃用 and is scheduled for removal in Python 3.10.

Generator-based coroutines predate async/await syntax. They are Python generators that use yield from expressions to await on Futures and other coroutines.

Generator-based coroutines should be decorated with @asyncio.coroutine , although this is not enforced.

@ asyncio. 协程

Decorator to mark generator-based coroutines.

This decorator enables legacy generator-based coroutines to be compatible with async/await code:

@asyncio.coroutine
def old_style_coroutine():
    yield from asyncio.sleep(1)
async def main():
    await old_style_coroutine()
				

This decorator should not be used for async def 协程。

从 3.8 版起弃用,将在 3.10 版中移除: 使用 async def 代替。

asyncio. iscoroutine ( obj )

返回 True if obj 协程对象 .

This method is different from inspect.iscoroutine() because it returns True for generator-based coroutines.

asyncio. iscoroutinefunction ( func )

返回 True if func 协程函数 .

This method is different from inspect.iscoroutinefunction() because it returns True for generator-based coroutine functions decorated with @coroutine .

版权所有  © 2014-2026 乐数软件    

工业和信息化部: 粤ICP备14079481号-1