Path: csiph.com!usenet.pasdenom.info!news.redatomik.org!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!newsgate.cistron.nl!newsgate.news.xs4all.nl!post.news.xs4all.nl!not-for-mail
MIME-Version: 1.0
In-Reply-To: <344fd8f6-75c1-4b7d-888d-c5c9d4498ec3@googlegroups.com>
References: <344fd8f6-75c1-4b7d-888d-c5c9d4498ec3@googlegroups.com>
From: Ian Kelly <ian.g.kelly@gmail.com>
Date: Tue, 5 May 2015 11:46:24 -0600
Subject: Re: asyncio: What is the difference between tasks, futures, and coroutines?
To: Python <python-list@python.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: list
Newsgroups: comp.lang.python
Message-ID: <mailman.130.1430848034.12865.python-list@python.org>
Lines: 49
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:89981

On Tue, May 5, 2015 at 9:22 AM, Paul  Moore <p.f.moore@gmail.com> wrote:
> I'm working my way through the asyncio documentation. I have got to the "=
Tasks and coroutines" section, but I'm frankly confused as to the differenc=
e between the various things described in that section: coroutines, tasks, =
and futures.
>
> I think can understand a coroutine. Correct me if I'm wrong, but it's rou=
ghly "something that you can run which can suspend itself".
>
> But I don't understand what a Future is. The document just says it's almo=
st the same as a concurrent.futures.Future, which is described as something=
 that "encapsulates the asynchronous execution of a callable". Which doesn'=
t help a lot. In concurrent.futures, you don't create Futures, you get them=
 back from submit(), but in the asyncio docs it looks like you can create t=
hem by hand (example "Future with run_until_complete"). And there's nothing=
 that says what a Future is, just what it's like... :-(

Fundamentally, a future is a placeholder for something that isn't
available yet. You can use it to set a callback to be called when that
thing is available, and once it's available you can get that thing
from it.

> A Task is a subclass of Future, but the documentation doesn't say what it=
 *is*, but rather that it "schedules the execution of a coroutine". But tha=
t doesn't make sense to me - objects don't do things, they *are* things. I =
thought the event loop did the scheduling?

In asyncio, a Task is a a Future that serves as a placeholder for the
result of a coroutine. The event loop manages callbacks, and that's
all it does. An event that it's been told to listen for occurs, and
the event loop calls the callback associated with that event. The Task
manages a coroutine's interaction with the event loop; when the
coroutine yields a future, the Task instructs the event loop to listen
for the completion of that future, setting a callback that will resume
the coroutine.

> Reading between the lines, it seems that the event loop schedules Tasks (=
which makes sense) and that Tasks somehow wrap up coroutines - but I don't =
see *why* you need to wrap a task in a coroutine rather than just schedulin=
g coroutines. And I don't see where Futures fit in - why not just wrap a co=
routine in a Future, if it needs to be wrapped up at all?

The coroutines themselves are not that interesting of an interface;
all you can do with them is resume them. The asynchronous execution
done by asyncio is all based on futures. Because a coroutine can
easily be wrapped in a Task, this allows for coroutines to be used
anywhere a future is expected.

I don't know if I've done a good job explaining, but I hope this helps.