Next | Query returned 7 messages, browsing 1 to 10 | previous

History of commit frequency

CVS Commit History:


   2024-01-22 18:02:47 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-nest-asyncio: updated to 1.6.0

1.6.0
Unknown changes
   2024-01-16 07:15:26 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-nest-asyncio: updated to 1.5.9

v1.5.9
Fix patching an already running Proactor loop
   2023-09-17 19:50:31 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-nest-asyncio: updated to 1.5.8

v1.5.8
Add support for Python 3.12
   2023-08-01 14:19:45 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-nest-asyncio: updated to 1.5.7

1.5.7
Unknown changes
   2022-10-14 11:43:43 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-nest-asyncio: updated to 1.5.6

v1.5.6
Remove old travis file
   2022-04-06 17:08:31 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-nest-asyncio: updated to 1.5.5

v1.5.5
Potential fix for issue 65
   2022-01-31 18:47:22 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
py-nest-asyncio: added version 1.5.4

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.

Next | Query returned 7 messages, browsing 1 to 10 | previous