Flask SocketIO and future retirement of eventlet

[spmsh]

Hi @miguelgrinberg, have you seen or what do you think about the warning announcement on the home page of the eventlet project saying that

new usages of eventlet are now heavily discouraged

https://eventlet.readthedocs.io/en/latest/
https://eventlet.readthedocs.io/en/latest/migration.html#migration-guide

Since eventlet is the first choice when using Flask SocketIO, what would be the recommendation or change to be done? Any planned update of your Flask SocketIO lib to use asyncio instead of eventlet? What would be your recommendation/suggestion on this?

Thanks.

[miguelgrinberg]

Yes, I have seen it. The project is slowly winding down, so at this time I would not recommend its use on new projects.

[sylos]

Are you saying flask socketIO is winding down?

[miguelgrinberg]

Eventlet is winding down, so you should not use. Flask-SocketIO is fine, use it all you want.

[spmsh]

what would you recommend for existing project using flask_socketio ? move to asyncio (although I wouldn't know how), use gevent, or stay with current eventlet version (potentially forever). Thanks again.

[miguelgrinberg]

If eventlet works you can continue using it. Else, using regular threading is the safest. Gevent might also be okay. Asyncio is not an option as it isn't compatible with flask.

[spmsh]

flask 3.0 still doesn't support asyncio? I've found this in their document: https://flask.palletsprojects.com/en/3.0.x/async-await
thanks,

[miguelgrinberg]

Async support in Flask is incomplete at this time. The limitations are well explained in the page that you linked.