> it's is quite nice to use, at least compared to what I remember asyncio being like.
Yes, I agree. Fairly recently there's been anyio [0], which brings ideas from trio to other async libraries, in particular asyncio. E.g. it has equivalent of trio nurseries (what anyio calls "task groups") for implementing structured concurrency ideas in asyncio environments (saving you from headaches due to having to deal with tasks manually). Very neat way to use trio ideas when stuck on asyncio (e.g. for web apps). :)
anyio was also discussed in the latest Python Bytes episode [1].
Yes, I agree. Fairly recently there's been anyio [0], which brings ideas from trio to other async libraries, in particular asyncio. E.g. it has equivalent of trio nurseries (what anyio calls "task groups") for implementing structured concurrency ideas in asyncio environments (saving you from headaches due to having to deal with tasks manually). Very neat way to use trio ideas when stuck on asyncio (e.g. for web apps). :)
anyio was also discussed in the latest Python Bytes episode [1].
[0]: https://github.com/agronholm/anyio
[1]: https://pythonbytes.fm/episodes/show/197/structured-concurre...