Closed WinPlay02 closed 10 months ago
Is this related to the issue reported by @SmiteDeluxe?
Websockets seem to be supported out-of-the-box by quart
. How could socket.io
be integrated (just spto ensure we don't lose options by migrating)? I guess python-socketio
could be used for this purpose?
litestar
might also be a lightweight ASGI framework to consider.
Is this related to the issue reported by @SmiteDeluxe?
This is the same issue
Websockets seem to be supported out-of-the-box by
quart
. How couldsocket.io
be integrated (just see to ensure we don't lose options by migrating? I guesspython-socketio
could be used for this purpose?
The python-socketio
library is the way to go, exactly. python-socketio
received support for ASGI a long time ago.
litestar
might also be a lightweight ASGI framework to consider.
I chose quart
as it is the successor to flask
and it seemed the most lightweight. I additionally also considered fastapi
.
Also see the fix-linux-startup-error
branch, for a preview.
Furthermore, a migration to the socket.io protocol is still possible although not as easy as changing the dependency in flask.
The potential future usage of was socket.io
was considered in the choice of quart
.
:tada: This issue has been resolved in version 0.5.0 :tada:
The release is available on:
v0.5.0
Your semantic-release bot :package::rocket:
Describe the bug
The runner crashes on first request (usually program message)
To Reproduce
Expected behavior
The runner executes the program
Screenshots (optional)
No response
Additional Context (optional)
I would propose to replace the (legacy) flask stack with a quart (successor in a way of flask) stack that does not require monkey patching python internals. This has the added benefit to allow async python functions and in turn being possibly more efficient.
Furthermore, a migration to the socket.io protocol is still possible although not as easy as changing the dependency in flask.