The classasyncio.Runner currently checks explicitly that its coro argument is a coroutine:

However, shouldn't this allow any awaitable, checked viainspect.isawaitable(), or perhaps aligned withrun_until_complete(), which currently accepts aFuture object? Is there a specific reason why only coroutines are allowed here?

I've got a class which implements a custom__await__() method that I'd like to be able to pass into asyncio.Runner, but the check above is preventing this. There are workaround for this, like wrapping the await on the object in a regular async function, but I'd prefer not to require that.

Linked PRs

• gh-120284: Enableasyncio.runners.Runner to run an awaitable object. #120306
• gh-120284: Enhance asyncio.Runner's run() method to accept more object types #120566