Question: what's the morale behind having a `asyncio.Future`? about asyncio

[gvanrossum]

I presume you meant "rationale", not "morale". :-)

I'm not sure where you're going with this question -- are you asking why there are two Future types instead of one? Or are you wondering why they both have the same name? Or why they have different behavior?

I'm not sure how to answer any of those, because I don't know what context you already have about concurrent programming. But perhaps the Wikipedia article on Futures and promises is helpful?

[ldo]

Differences are listed here. It seems clear that asyncio.Future avoids any semantics that might implicitly block the caller; instead, such blocking must be explicit, through the await construct.