[issue25675] doc for BaseEventLoop.run_in_executor() says its a coroutine, but it is not

Andrew Svetlov added the comment: It was always awaitable object, in Python 3.7 the method was converted into genuine coroutine. -- nosy: +asvetlov ___ Python tracker

[issue25675] doc for BaseEventLoop.run_in_executor() says its a coroutine, but it is not

Change by Andrew Svetlov : -- resolution: -> fixed stage: -> resolved status: open -> closed ___ Python tracker ___

[issue25675] doc for BaseEventLoop.run_in_executor() says its a coroutine, but it is not

Ian Kelly added the comment: The asyncio docs also have this note, so this is technically not a bug: Note: In this documentation, some methods are documented as coroutines, even if they are plain Python functions returning a Future. This is intentional to have a freedom of tweaking the

[issue25675] doc for BaseEventLoop.run_in_executor() says its a coroutine, but it is not

Changes by Guido van Rossum : -- keywords: +easy priority: normal -> low ___ Python tracker ___

[issue25675] doc for BaseEventLoop.run_in_executor() says its a coroutine, but it is not

Changes by Nicolas Demarchi : -- nosy: +gilgamezh ___ Python tracker ___ ___

[issue25675] doc for BaseEventLoop.run_in_executor() says its a coroutine, but it is not

New submission from Ezequiel Alfie: Doc says: coroutine BaseEventLoop.run_in_executor(executor, func, *args) .. This method is a coroutine. However, inspecting the code, I find that this function is not a coroutine. Also this function returns a Future instance, this fact should be