4 ms·
async/await code already runs in threads, so that's not really a change.
by gjulianm 3y ago
async/await code already runs in threads, so that's not really a change.
- quietbritishjim 3y agoWhat do you mean it already runs in threads? It does so if you specify it with run_in_executor [1], or if you run multiple event loops at once, but it doesn't automatically. [1] https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.run_in_executor https://docs.python.org/3/library/asyncio-eventloop.html#asy...
- gjulianm 3y agoWoops, yeah, you're right. I thought the default executor was a threadpool, my mistake. However, in that case, I assume that the default executor will not change to multithreaded when no-gil comes.
- quietbritishjim 3y agoThere isn't an executor at all, at least not in the concurrent.futures.Executor sense. It just runs in the thread where you call asyncio.run.