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 Yury.Selivanov
Recipients Yury.Selivanov, gvanrossum, python-dev, r.david.murray, vstinner, vxgmichel, yselivanov
Date 2015-10-04.18:13:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <809A780E-CBFE-4FFD-A21F-D7FCFF9066DA@gmail.com>
In-reply-to <1443974370.94.0.211082401568.issue25304@psf.upfronthosting.co.za>
Content
> But honestly I *don't* want to encourage flipping back and forth between threads and event loops; I see it as a necessary evil. The name we currently have is fine from the POV of someone coding in the threaded world who wants to hand off something to the asyncio world.

I agree, but on the other hand supporting awaitables in addition to coroutines would be great. Can we at least add that?
History
Date User Action Args
2015-10-04 18:13:44Yury.Selivanovsetrecipients: + Yury.Selivanov, gvanrossum, vstinner, r.david.murray, python-dev, yselivanov, vxgmichel
2015-10-04 18:13:44Yury.Selivanovlinkissue25304 messages
2015-10-04 18:13:44Yury.Selivanovcreate