aboutsummaryrefslogtreecommitdiff
path: root/python/python3-nest_asyncio/README
diff options
context:
space:
mode:
authorIsaac Yu <isaacyu@protonmail.com>2024-03-07 10:25:22 +0700
committerWilly Sudiarto Raharjo <willysr@slackbuilds.org>2024-03-09 06:18:09 +0700
commit3f56a0aad1d2415b332b8eaae0a8ba296de3e10d (patch)
tree6e8376e71233c8c21ee6eccf3e669c2470d16d80 /python/python3-nest_asyncio/README
parentf11bf307d52376626a163c51fef5f9c2b5f33ec0 (diff)
python/python3-nest_asyncio: Added (python3 of nest_asyncio).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'python/python3-nest_asyncio/README')
-rw-r--r--python/python3-nest_asyncio/README11
1 files changed, 11 insertions, 0 deletions
diff --git a/python/python3-nest_asyncio/README b/python/python3-nest_asyncio/README
new file mode 100644
index 0000000000..cb355b2261
--- /dev/null
+++ b/python/python3-nest_asyncio/README
@@ -0,0 +1,11 @@
+By design asyncio does not allow its event loop to be nested. This
+presents a practical problem: When in an environment where the event
+loop is already running it's impossible to run tasks and wait for the
+result. Trying to do so will give the error "RuntimeError: This event
+loop is already running".
+
+The issue pops up in various environments, such as web servers, GUI
+applications and in Jupyter notebooks.
+
+This module patches asyncio to allow nested use of asyncio.run and
+loop.run_until_complete.