From d39628129373d3b6e36e835789364b2eaae63fd6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Herv=C3=A9=20Beraud?= Date: Wed, 27 Mar 2024 13:48:54 +0100 Subject: [PATCH] [trivial] linkage awesome-asyncio into our migration guide (#947) --- doc/source/migration.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/source/migration.rst b/doc/source/migration.rst index ebecffddc..2aeb72c5f 100644 --- a/doc/source/migration.rst +++ b/doc/source/migration.rst @@ -83,6 +83,10 @@ Cancellation of ``asyncio.Future`` and killing of ``eventlet.GreenThread`` shoul Using these two APIs, with more to come, you can gradually migrate portions of your application or library to ``asyncio``. Calls to blocking APIs like ``urlopen()`` or ``requests.get()`` can get replaced with calls to ``aiohttp``, for example. +The `awesome-asyncio `_ github repository propose a curated list of awesome +Python asyncio frameworks, libraries, software and resources. Do not hesitate to take a look at it. You may find +candidates compatible with asyncio that can allow you to replace some of your actual underlying libraries. + Step 3. Drop Eventlet altogether --------------------------------