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 scoder
Recipients gvanrossum, scoder, vstinner, yselivanov
Date 2015-06-06.09:33:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1433583214.86.0.0598301442581.issue24383@psf.upfronthosting.co.za>
In-reply-to
Content
(Copying my review comment here so that it doesn't get lost as it's more of a general design thing than a specific review comment.)

Having Future know and deal with asyncio seems wrong to me. asyncio should be able to deal *somehow* with a Future that is being awaited, but a Future shouldn't require asyncio in order to be awaited.
History
Date User Action Args
2015-06-06 09:33:34scodersetrecipients: + scoder, gvanrossum, vstinner, yselivanov
2015-06-06 09:33:34scodersetmessageid: <1433583214.86.0.0598301442581.issue24383@psf.upfronthosting.co.za>
2015-06-06 09:33:34scoderlinkissue24383 messages
2015-06-06 09:33:34scodercreate