Darn. The one issue is that iscoroutine returns True if the value is a generator, this breaks the list resolver in the case of a generator.

Thanks for your PR. I'm currently very busy, but will look into this when I find time. Maybe we can find a solution for that issue with generators. We also need to check how much this change is visible in the performance tests (activate with --benchmark-enable when running the tests).

Coroutines and awaitables are different things.

Coroutines refer to async functions, while awaitables refer to the result of running async functions.

isawaitable is the right thing to ask for, if you are asking in the data. We could ask on iscoroutine in the function, but this make the following to not work:

async def my_async_func():
 return 1
def resolve_x(root, info, **args):
 return my_async_func()
assert iscoroutine(resolve_x) == False
assert isawaitable(resove_x()) == True

Closing the PR

@syrusakbary asyncio.iscoroutine actually checks for coroutine objects. In your example, you do not call resolve_x() in the first assert statement, otherwise it would be equal to True.

I have removed my last misleading comment. The problem with asyncio.iscoroutine is not that it does not detect old-syle generator-based coroutine.

But the problems with asyncio.iscoroutine instead of isawaitable are:

1. it returns True for generators (as @corydolphin already commented),
2. it returns False for Futures because they are not coroutines.