Documentation

asyncio-dev docs claim:

asyncio checks forcoroutines that were not awaited and logs them; this mitigates the “forgotten await” pitfall.

and the docs that points to claim:

When a coroutine function is called, but not awaited (e.g. coro() instead of await coro()) or the coroutine is not scheduled withasyncio.create_task(), asyncio will emit aRuntimeWarning:

this isn't true, python will produce warnings when coroutines are not awaited regardless of the dev mode of asyncio. The flag to set is-Werror and then replacesys.unraisablehook to detect these

I think this is a hold-over from when asyncio had generator based coroutines.

Linked PRs

• gh-133515: fix docs for unawaited coroutines in debug mode #134081
• [3.14] gh-133515: fix docs for unawaited coroutines in debug mode (GH-134081) #134093
• [3.13] gh-133515: fix docs for unawaited coroutines in debug mode (GH-134081) #134094