Is Python async/await some kind of joke?

Question

Returning to Python full-stack development after a stint with Node, it seems like using async/await is not widely adopted enough in the Python ecosystem to actually use?In no particular order- Django doesn&rsquo;t have an async ORM? (https://docs.djangoproject.com/en/5.0/topics/async/)- Django Rest Framework has no async support? https://github.com/encode/django-rest-framework/issues/7260- SQLModel&rsquo;s section on async support basically says &ldquo;docs coming soon&rdquo;? Yet this is designed to be used with FastAPI? Why would the docs not start with async/await? https://sqlmodel.tiangolo.com/advanced/- SqlAlchemy/asyncpg => you can&rsquo;t use it if you&rsquo;re using PgBouncer (necessary most of the time with Postgres) in transaction mode? What?? https://github.com/MagicStack/asyncpg/issues/1058- Ubiquitous &ldquo;requests&rdquo; library used in most docs examples, no async support https://github.com/psf/requests- Top package for GitHub REST API, no async support https://github.com/PyGithub/PyGithub- &hellip;on and on&hellip;What&rsquo;s the point of my nice FastAPI server if nothing internally can use async/await? How is everyone else doing this?/rant

vlz · Accepted Answer

Personally I am fine doing python/Django fullstack without it and never felt the need to use async/await.
I was interested in the situation with the Django ORM however. The page you linked to seems somewhat contradictory. In the section on "Queries and the ORM" it seems that there are asynchronous versions for most queries that actually cause an SQL query:
https://docs.djangoproject.com/en/5.0/topics/async/#queries-...
These should also be fine to be executed in an async context, right? But then later in the section on async safety it somewhat seems like the ORM is totally prevented from being executed in an asynchronous manner:
https://docs.djangoproject.com/en/5.0/topics/async/#async-sa...
The linked section on orm queries however makes it seem like it should be possible to use the Django ORM asynchronously if you only use the async methods (aget, aupdate, async for, ...) and watch out for some gotchas:
https://docs.djangoproject.com/en/5.0/topics/db/queries/#asy...

raverbashing · Answer

Let me say that I'm of the opinion that async/await just became popular because js didn't have any better way of doing concurrent programming
Having one thread per worker sounds better. Or the actor model
Sure async/await is "easy" but also turns every code into a mess

cpburns2009 · Answer

I generally find threaded code easier to work with, especially with WSGI applications (one thread per request). The only time I find async code helpful is to prevent callback hell like when using PySide6 or JavaScript on the front-end.

Is Python async/await some kind of joke?

Let me say that I'm of the opinion that async/await just became popular because js didn't have any better way of doing concurrent programmingHaving one thread per worker sounds better. Or the actor modelSure async/await is "easy" but also turns every code into a mess

I generally find threaded code easier to work with, especially with WSGI applications (one thread per request). The only time I find async code helpful is to prevent callback hell like when using PySide6 or JavaScript on the front-end.

Let me say that I'm of the opinion that async/await just became popular because js didn't have any better way of doing concurrent programming
Having one thread per worker sounds better. Or the actor model
Sure async/await is "easy" but also turns every code into a mess