In PEP-525, async generators were introduced. They use .asend() and .athrow() methods that return a "coroutine-like" object - specifically, a PyAsyncGenASend and PyAsyncGenAThrow respectively.

While these "coroutine-like" object implement .send(), .throw(), and .close(), they don't provide any attributes like normal coroutine objects do such as cr_running or cr_await.

When I use inspect.getcoroutinestate(), it raises an AttributeError on how there isn't a cr_running attribute / flag.

There is a workaround I use which is to wrap it with another coroutine as below:

>>> async def async_generator():
...     yield
...
>>> async def wrap_coro(coro):
...     return await coro
>>> agen = async_generator()
>>> asend = wrap_coro(agen.asend(None))

This seems like something that should be changed to make it more inline with normal coroutines / awaitables.

Duplicate of #79940.

i think that this may not be a duplicate of GH-79940. if i understand correctly:

• inspect module does not implement introspection API for asynchronous generators #79940 is about inspecting the state of an async generator object. it was resolved when inspect.getasyncgenstate/inspect.getasyncgenlocals was added.

• this thread is about inspecting the state of an agen.asend(...) "coroutine-like" object (i.e. PyAsyncGenASend, AKA async_generator_asend on CPython). AFAICT it is still not possible to inspect the state of a PyAsyncGenASend unless you wrap it.