Python asyncio.timeout: catch the deadline outside the context

Operation contract

The owned Event is never set, so the wait cannot finish normally. A zero-second deadline cancels the current task at its next suspension; the context converts that cancellation into TimeoutError on exit. The caller catches it outside the context and records a rejected receipt lookup. No network call or wall-clock sleep is needed to show the boundary.

Failure and ownership boundary

The timeout limits the awaiting task, not arbitrary blocking work already moved to a thread or remote service. Cleanup in finally still needs its own failure and time budget, and swallowing CancelledError inside the context can defeat the intended deadline. Python asyncio timeout: cancellation and cleanup ownership, Python asyncio.to_thread: carry context into blocking work and Python asyncio shield: caller cancellation does not transfer task ownership describe adjacent ownership rules.

Working program

import asyncio

async def wait_for_receipt():
    gate = asyncio.Event()
    try:
        async with asyncio.timeout(0):
            await gate.wait()
    except TimeoutError:
        return "lookup timed out"
    return "receipt arrived"

print(asyncio.run(wait_for_receipt()))

Output

lookup timed out

Costs and limits

The fixture creates one Event and task. A real deadline must include queueing, transport and cleanup costs; timing behavior under load is not established by this deterministic expired-deadline case.

Common Mistakes

• Catch TimeoutError around the context, not inside it.
• Cancelling the await does not prove a remote or threaded side effect stopped.

Connected lessons

Python asyncio timeout: cancellation and cleanup ownership, Python asyncio.to_thread: carry context into blocking work, Python asyncio shield: caller cancellation does not transfer task ownership.