From a20123864bed93abc11944f486cca528ab918369 Mon Sep 17 00:00:00 2001 From: nocturn9x Date: Thu, 3 Jun 2021 16:39:22 +0200 Subject: [PATCH] Minor fix --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7ad1ab4..5d3b5eb 100644 --- a/README.md +++ b/README.md @@ -24,7 +24,7 @@ further I found some issues with the current async ecosystem in Python. As of the time of writing, the ecosystem for async libraries is divided as follows: - Asyncio. Since it's in the stdlib, it sets a standard all of its own - Tornado/Gevent/other old frameworks (based partly on asyncio or not) -- Modern, post PEP 492 frameworks like curio and trio +- Modern, post-PEP 492 frameworks like curio and trio The main issue with asyncio is too complex to explain here in detail, but in short it boils down to the fact that it is an old library which was not designed to take advantage