diff options
| author | B. Watson <yalhcru@gmail.com> | 2022-03-14 11:05:02 -0400 |
|---|---|---|
| committer | B. Watson <yalhcru@gmail.com> | 2022-03-17 12:37:55 -0400 |
| commit | 7cc2f572fba5a2cd5123053b7cba6b573b6989f8 (patch) | |
| tree | fc9e77918cc6b1f8caf6a0f33392ddb5e3feadf0 /python/nest_asyncio | |
| parent | 1286eefcf5663a3fee8e396be6b99deb03055cd2 (diff) | |
python/nest_asyncio: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'python/nest_asyncio')
| -rw-r--r-- | python/nest_asyncio/README | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/python/nest_asyncio/README b/python/nest_asyncio/README index 212658bb3116..cb355b2261cb 100644 --- a/python/nest_asyncio/README +++ b/python/nest_asyncio/README @@ -1,7 +1,8 @@ -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". +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. |