➜

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 yselivanov
Recipients alex.gronholm, asvetlov, gvanrossum, ncoghlan, python-dev, scoder, vstinner, yselivanov
Date 2015-06-03.15:18:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433344733.37.0.617991180931.issue24017@psf.upfronthosting.co.za>
In-reply-to
Content 
> Was __await__() deliberately left out of concurrent.futures.Future or was that an oversight? Or am I misunderstanding something?

I don't think concurrent.Future is supposed to be used with asyncio (in 'yield from' or 'await' expressions).
History
Date User Action Args
2015-06-03 15:18:53yselivanovsetrecipients: + yselivanov, gvanrossum, ncoghlan, scoder, vstinner, asvetlov, alex.gronholm, python-dev
2015-06-03 15:18:53yselivanovsetmessageid: <1433344733.37.0.617991180931.issue24017@psf.upfronthosting.co.za>
2015-06-03 15:18:53yselivanovlinkissue24017 messages
2015-06-03 15:18:53yselivanovcreate