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.

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 <>
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.
Date User Action Args
2015-07-07 12:23:59ncoghlansetrecipients: + ncoghlan, gvanrossum, pitrou, vstinner, giampaolo.rodola, yselivanov, srkunze
2015-07-07 12:23:59ncoghlansetmessageid: <>
2015-07-07 12:23:59ncoghlanlinkissue24571 messages
2015-07-07 12:23:59ncoghlancreate