We had seen issues in Badfish where newer Python 3.14 is stricter about event_loop usage. I believe this can break QUADS too.
asyncio.get_event_loop() no longer implicitly creates a loop when none exists in the current thread — it raises RuntimeError instead (and in some cases deprecations/warnings apply to related policy functions like set_event_loop or get_event_loop_policy).
"The get_event_loop() method of the default asyncio policy now emits a DeprecationWarning if there is no current event loop set and it decides to create one. In some future Python release [3.14], this will become an error."
https://docs.python.org/3/library/asyncio-policy.html
We had seen issues in Badfish where newer Python 3.14 is stricter about event_loop usage. I believe this can break QUADS too.
asyncio.get_event_loop() no longer implicitly creates a loop when none exists in the current thread — it raises RuntimeError instead (and in some cases deprecations/warnings apply to related policy functions like set_event_loop or get_event_loop_policy).
"The get_event_loop() method of the default asyncio policy now emits a DeprecationWarning if there is no current event loop set and it decides to create one. In some future Python release [3.14], this will become an error."
https://docs.python.org/3/library/asyncio-policy.html