Python has had async for 10 years – why isn't it more popular?

Re:Python has had async for 10 years – why isn't it more pop... by tylerhou on Tuesday September 02, 2025 @07:00PM (#45110231)

> You can end up writing nearly the exact same code twice because one needs to be async to handle an async function argument, even if the real functionality of the wrapper isn't async.

Sorry for the possibly naive question. If I need to call a synchronous function from an async function, why can't I just call await on the async argument?

    def foo(bar: str, baz: int):
      # some synchronous work
      pass
    
    async def other(bar: Awaitable[str]):
      foo(await bar, 0)

[ Parent | on HN ]

Re:Python has had async for 10 years – why isn't it more pop... by gcharbonnier on Thursday September 04, 2025 @02:39PM (#45130703)

Nothing and that’s the problem because even though you can do it, your event loop will block until foo has finished executing, meaning that in this thread no other coroutine will be executed in the meantime (an event loop runs in its own thread. Most of the time there is only the main thread thus a single event loop). This defeats the purpose of concurrent programming.

[ Parent | on HN ]