Message246404
| Author |
ncoghlan |
| Recipients |
giampaolo.rodola, gvanrossum, ncoghlan, pitrou, srkunze, vstinner, yselivanov |
| Date |
2015年07月07日.12:23:59 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1436271839.79.0.0327628216172.issue24571@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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. |
|