mirror of https://github.com/nocturn9x/giambio.git
Minor fix
This commit is contained in:
parent
792399744f
commit
a20123864b
|
@ -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:
|
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
|
- 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)
|
- 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
|
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
|
it boils down to the fact that it is an old library which was not designed to take advantage
|
||||||
|
|
Loading…
Reference in New Issue