2 ms·

I think you are right on every point, which is why we should agree that using python async is a bad decision and anyone starting a new project should not use it

I think you are right on every point, which is why we should agree that using python async is a bad decision and anyone starting a new project should not use it. Threads might not be what all the cool LLMs are doing, but I have never spent half of all my work time for a month debugging a threading bug, much less half of my day every day forever like with python async. Anyone who says they don't spend half their time debugging python async internals either doesn't use it or doesn't realize they are spending 500x too much on hosting.

zbentley 2mo ago
I’m not sure I’d go as far as “always a bad decision”, but Python async is definitely something that shouldn’t be adopted without carefully considering alternatives and being aware of the requisite expertise needed. It’s an advanced and sharp-edged tool, and I wish people forced to use it (e.g. due to the use of libraries that only expose an async API) had better tools to make its limited adoption in an otherwise-sync codebase easier. Especially in Python, threads and blocking code should definitely be encouraged as a first resort.