[issue33117] asyncio example uses non-existing/documented method

Andrew Svetlov added the comment: @xtreak is right, `run_coroutine_threadsafe()` returns `concurrent.futures.Future` object. Personally, I like the fact that `fut.result()` is called with timeout parameter to reflect the fact of the different object type. -- resolution: -> not a

[issue33117] asyncio example uses non-existing/documented method

Karthikeyan Singaravelan added the comment: I think `asyncio.run_coroutine_threadsafe(coro, loop)` returns a concurrent.futures.Future [1] which supports timeout and not asyncio.Future which doesn't support timeout. Please add in if I am missing anything. Since asyncio docs are being

[issue33117] asyncio example uses non-existing/documented method

Change by Terry J. Reedy : -- versions: -Python 3.5 ___ Python tracker ___ ___

[issue33117] asyncio example uses non-existing/documented method

Change by Ned Deily : -- nosy: +asvetlov, giampaolo.rodola, yselivanov ___ Python tracker ___

[issue33117] asyncio example uses non-existing/documented method

New submission from Henrique Fingler : In the documentation of asyncio.run_coroutine_threadsafe(coro, loop), in Section 19.5.3.6 (https://docs.python.org/3/library/asyncio-task.html#asyncio.run_coroutine_threadsafe), the example code does the following: future =