➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2015-08-03 11:44 by alex.gronholm, last changed 2022-04-11 14:58 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg247924 - (view) | Author: Alex Grönholm (alex.gronholm) * | Date: 2015-08-03 11:44 | |
Since Python 3.5 will not support awaiting for concurrent.futures.Futures natively, one has to use the asyncio.futures.wrap_future() function in coroutines like this:
async def foo():
await wrap_future(executor.submit(...))
The wrap_future() function is, however, not mentioned in the asyncio documentation. It should be, in order for the standard library to provide the above crutch until proper support arrives in 3.6.
|
|||
| msg247926 - (view) | Author: Berker Peksag (berker.peksag) *  |
Date: 2015-08-03 12:04 | |
This is a duplicate of issue 24755. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:58:19 | admin | set | github: 68973 |
| 2015-08-03 12:31:27 | yselivanov | set | nosy:
+ yselivanov |
| 2015-08-03 12:04:02 | berker.peksag | set | status: open -> closed superseder: asyncio.wrap_future undocumented nosy: + berker.peksag messages: + msg247926 resolution: duplicate stage: resolved |
| 2015-08-03 11:44:43 | alex.gronholm | create | |