Re:A viable solution for Python concurrency
by BiteCode_dev on Sunday October 17, 2021 @06:15AM
(#28895329)
The idea is that once task groups are implemented, you can switch back to asyncio, which as more chance than Trio to be supported.
Trio has the better API, so you might as well use that directly rather some other library that attempts to match it, even if it can/does use it under the hood. It reminds me of that xkcd about standards. It's also going to have to settle for the least common denominator to some extent even if it reimplements some parts itself (e.g. if one library implements serial ports but the other didn't, then it surely can't be in anyio). I also dispute that it's "more future proof", because you're still relying on anyio being maintained, and to me it seems to be the more obscure library.