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?
- SQLModel’s section on async support basically says “docs coming soon”? Yet this is designed to be used with FastAPI? Why would the docs not start with async/await? https://sqlmodel.tiangolo.com/advanced/
In no particular order
- Django doesn’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’s section on async support basically says “docs coming soon”? 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’t use it if you’re using PgBouncer (necessary most of the time with Postgres) in transaction mode? What?? https://github.com/MagicStack/asyncpg/issues/1058
- Ubiquitous “requests” 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
- …on and on…
What’s the point of my nice FastAPI server if nothing internally can use async/await? How is everyone else doing this?
/rant