Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
115 changes: 115 additions & 0 deletions Doc/library/asyncio-dev.rst
Original file line number Diff line number Diff line change
Expand Up @@ -248,3 +248,118 @@
File "../t.py", line 4, in bug
raise Exception("not consumed")
Exception: not consumed


Asynchronous generators best practices
======================================
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd insert some friendly words here introducing the reader to the purpose of this section. Right now it looks rather stern.


By :term:`asynchronous generator` in this section we will mean
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems obvious, by generator we typically mean the generator object not the function.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I saw this clarification in few places (e.g. https://docs.python.org/3/glossary.html#term-asynchronous-generator), so I thought it was worth mentioning. I'm OK to remove this if you think so.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In my experience, the term "generator" is used equally for a generator function and for the iterator returned by calling a generator function. If you really only use it for the latter, then this clarification makes sense.

an :term:`asynchronous generator iterator` that is returned by an
:term:`asynchronous generator` function.


Manually close the generator
----------------------------

If an asynchronous generator happens to exit early by :keyword:`break`, the caller
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feels too heavy for start, I would start it as "It is recommended to manually close the generator... " then in second para describe the issue with breaking early.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, will fix this.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIUC the scenario(s) you are trying to describe is where the code iterating over the generator doesn't iterate till the end. If you're iterating over it using a for-loop (there are other ways!) that could be a break in that for-loop, or the task containing that for-loop getting canceled, or indeed an exception being raised in the for-loop body. But I'm not sure it's helpful to try to list all the reasons why this can happen -- maybe the most useful one to mention is an exception being raised during that for-loop?

(The example code clarifies a lot!)

task being cancelled, or other exceptions, the generator's async cleanup code
will run in an unexpected context -- perhaps after the lifetime of tasks it depends on, or
during the event loop shutdown when the async-generator garbage collection hook
is called.

To prevent this, it is recommended to explicitly close the async generator by
calling the :meth:`~agen.aclose` method, or using a :func:`contextlib.aclosing` context
manager::

import asyncio
import contextlib

async def gen():
yield 1
yield 2

async def func():
async with contextlib.aclosing(gen()) as g:
async for x in g:
break # Don't iterate until the end

asyncio.run(func())


Only create a generator when a loop is already running
------------------------------------------------------

It is recommended to create asynchronous generators only after the event loop
has already been created.

To ensure that asynchronous generators close reliably, the event loop uses the
:func:`sys.set_asyncgen_hooks` function to register callback functions. These
callbacks update the list of running asynchronous generators to keep it in a
consistent state.

When the :meth:`loop.shutdown_asyncgens() <asyncio.loop.shutdown_asyncgens>`
function is called, the running generators are stopped gracefully, and the
list is cleared.

The asynchronous generator calls the corresponding system hook when on the
first iteration. At the same time, the generator remembers that the hook was
called and don't call it twice.

So, if the iteration begins before the event loop is created, the event loop
will not be able to add it to its list of active generators because the hooks
will be set after the generator tries to call it. Consequently, the event loop
will not be able to terminate the generator if necessary.


Avoid iterating and closing the same generator concurrently
-----------------------------------------------------------

Async generators may to be reentered while another

Check warning on line 317 in Doc/library/asyncio-dev.rst

View workflow job for this annotation

GitHub Actions / Docs / Docs

py:meth reference target not found: agen.anext [ref.meth]
:meth:`~agen.anext`/:meth:`~agen.athrow`/:meth:`~agen.aclose` call is in
progress. This may lead to an inconsistent state of the async generator
and can cause errors.

Let's consider following example::

import asyncio

async def consumer():
for idx in range(100):
await asyncio.sleep(0)
message = yield idx
print('received', message)

async def amain():
agenerator = consumer()
await agenerator.asend(None)

fa = asyncio.create_task(agenerator.asend('A'))
fb = asyncio.create_task(agenerator.asend('B'))
await fa
await fb

asyncio.run(amain())

Output::

received A
Traceback (most recent call last):
File "test.py", line 38, in <module>
asyncio.run(amain())
~~~~~~~~~~~^^^^^^^^^
File "Lib\asyncio\runners.py", line 204, in run
return runner.run(main)
~~~~~~~~~~^^^^^^
File "Lib\asyncio\runners.py", line 127, in run
return self._loop.run_until_complete(task)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^
File "Lib\asyncio\base_events.py", line 719, in run_until_complete
return future.result()
~~~~~~~~~~~~~^^
File "test.py", line 36, in amain
await fb
RuntimeError: anext(): asynchronous generator is already running


Therefore, it is recommended to avoid using async generators in parallel
tasks or from multiple event loops.
Loading