What is the difference between a coroutine, an asyncio Task, and a Future?

Explains awaitable work, scheduled ownership, and eventual-result integration in asyncio.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Calling an async def function creates a coroutine object; it does not run the body by itself. Awaiting the coroutine runs it as part of the current task. An asyncio Task schedules a coroutine on the running event loop and owns its result, exception, or cancellation state. A Future is a lower-level awaitable placeholder for a result that will be supplied later, often by event-loop or library integration.

Full answer below

Practice focus

Explains awaitable work, scheduled ownership, and eventual-result integration in asyncio.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
Explains awaitable work, scheduled ownership, and eventual-result integration in asyncio.
Calling an async def function creates a coroutine object; it does not run the body by itself. Awaiting the coroutine runs it as part of the current task. An asyncio Task schedules a coroutine on the running event loop and owns its result, exception, or cancellation state. A Future is a lower-level awaitable placeholder for a result that will be supplied later, often by event-loop or library integration.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I usually expose coroutines from application APIs and let a clear parent decide whether to await them sequentially or schedule tasks concurrently. Tasks matter when operations need overlapping lifetimes, names, cancellation, and exception observation. I rarely create raw futures in business code because they are coordination primitives, not units of work; callback-style integrations may use them to bridge completion into awaitable code.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Calling a coroutine and assuming it started
Using Future as a general background job
Creating tasks without an owner

What is the difference between a coroutine, an asyncio Task, and a Future?

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue the section

Tech stacks

Skill areas

Suggest an improvement

Found this answer useful?