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 gvanrossum
Recipients Yury.Selivanov, gvanrossum, python-dev, r.david.murray, vstinner, vxgmichel, yselivanov
Date 2015-10-04.20:21:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1443990100.4.0.131180192663.issue25304@psf.upfronthosting.co.za>
In-reply-to
Content
@rdm: thanks, you nailed it. :-)

@yury: but where would you have gotten the awaitable in the first place? It's easy to see how to get a coroutine -- just define it (with either @coroutine or async def) and call it -- and I think that's the only use case that matters here.

I'm unclear how you could have gotten another awaitable (e.g. an asyncio.Future instance) in another thread -- except by an utterly confused user.
History
Date User Action Args
2015-10-04 20:21:40gvanrossumsetrecipients: + gvanrossum, vstinner, r.david.murray, Yury.Selivanov, python-dev, yselivanov, vxgmichel
2015-10-04 20:21:40gvanrossumsetmessageid: <1443990100.4.0.131180192663.issue25304@psf.upfronthosting.co.za>
2015-10-04 20:21:40gvanrossumlinkissue25304 messages
2015-10-04 20:21:40gvanrossumcreate