31–36 of 36 posts
https://github.com/sysid/sse-starlette makes token streaming so much easier in python
The actual biggest pain for me has been the front end handling of it with the fetch api. But that’s likely just due my inexperience with it.
To those who have been around longer than me: isn’t this just long polling, that predates websocket?
Do modern chat actually use websocket and the like? Discord / Slack on the web ( browser ) what do they use?
Earlier quoted context omitted.
Look at the intended semantics [1], and then read the implementation [2]. Can you figure out if the implementation is correct? Can you infer the possible limitations of the approach at glance? Can your async library actually handle being called with multiple event loops installed? I have zero trust in this code and I have been bitten by fixes to this library that introduced deadlocks in my own code. [1] https://githu…
Doesn't look like something I'd want to have to debug in a pinch, that's for sure. Is there anything else in Python-land you would go with for the use case you have in mind? Or does pretty much all the async stuff turn on you like this, at some point or another?
- pick a mature ASGI server
- pick a framework and libraries that have been designed from the start with async in mind. Be suspicious of libraries that support sync and async APIs without clear guard rails between the too implementations
- avoid setups where you have multiple event loops in a single process.
Earlier quoted context omitted.
Doesn't look like something I'd want to have to debug in a pinch, that's for sure. Is there anything else in Python-land you would go with for the use case you have in mind? Or does pretty much all the async stuff turn on you like this, at some point or another?
If you need to buy into the async ecosystem for some special reason my recomendation is to: - pick a mature ASGI server - pick a framework and libraries that have been designed from the start with async in mind. Be suspicious of libraries that support sync and async APIs without clear guard rails between the too implementations - avoid setups where you have multiple event loops in a single process.
Just a heads up that currently Django is not cleaning up open PostgreSQL connections when ran in ASGI mode, leading to too many open connections error: https://code.djangoproject.com/ticket/33497
Reading that bug report it looks like Django hasn't been isolated as the source of the problem? Looks like Carlton Gibson closed it until it is reproducible. Problem could be in uvicorn, psycopg2, etc