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, r.david.murray, srkunze, vstinner, yselivanov
Date 2015-07-09.13:21:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'll at least write a new python-ideas post, as I realised my original idea *is* wrong (and you're right not to like it). The focus needs to be on Sven's original question (How do you kick off a coroutine from otherwise synchronous code, and then later wait for the result?), and then asking whether or not it might make sense to provide a convenience API for such an interface between the worlds of imperative programming and event-driven programming.

Sven's far from the only one confused by that particular boundary, so even if a convenience API doesn't make it into the module itself, an example in the docs explaining how to implement it may be helpful.
Date User Action Args
2015-07-09 13:21:23ncoghlansetrecipients: + ncoghlan, gvanrossum, pitrou, vstinner, giampaolo.rodola, r.david.murray, yselivanov, srkunze
2015-07-09 13:21:23ncoghlansetmessageid: <>
2015-07-09 13:21:23ncoghlanlinkissue24571 messages
2015-07-09 13:21:23ncoghlancreate