Why Your JavaScript Async Pattern Silently Breaks in Python

A common JavaScript concurrency pattern — calling async functions early and awaiting them late — does not work the same way in Python, despite nearly identical syntax. In JavaScript, calling an async function immediately starts execution, returning a 'hot' promise already in flight before any await is reached. In Python, calling an async function creates an inert coroutine object; no code runs until an explicit await is issued. This means the JavaScript trick of overlapping two network calls runs them sequentially in Python, with no error or warning to signal the problem. The fix in Python requires tools like asyncio.gather() to explicitly schedule coroutines as concurrent tasks.