[Python-ideas] The async API of the future: Twisted and Deferreds

[Guido van Rossum]

On Sun, Oct 14, 2012 at 11:19 AM, Jasper St. Pierre
<jstpierre at mecheye.net> wrote:
> On Sun, Oct 14, 2012 at 2:17 PM, Guido van Rossum <guido at python.org> wrote:
>> The Future class itself probably shouldn't interface with the event
>> loop. But an operation that creates and returns a Future certainly
>> can.
>
> Of course, but that wouldn't be done at the Future level, but at the
> fetch_async level. I just want to make sure that we're clear that the
> Future itself isn't being registered with any event loop or reactor.

Of course.

-- 
--Guido van Rossum (python.org/~guido)