Nick Coghlan added the comment: The concerns I have with "get_awaitable" are:
* it doesn't express user intent - the user doesn't care about getting an awaitable, they want to initiate a blocking call without holding up the current coroutine * it's too broad - there are many other ways to get an awaitable, while this is specifically about being able to schedule a blocking call in another thread or process If "blocking_call" reminds you of the execution of f, that's a good thing: this call immediately dispatches f for execution in another thread or process, and returns a future that lets you wait for the result later. ---------- title: [RFE] Add asyncio.blocking_call API -> [RFE] Add asyncio.call_in_executor API _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24571> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
