asgiref

Certainly an interesting approach compared to asgiref or synchronicity but I have doubts about the approach. Does this not add further function colors - that of a transfunction, tiddle superfunction and non-tilde superfunction? Now every time you call one from another you need to use both the context managers and know what variant you are calling. asgiref provides the simple wrappers sync_to_async() and async_to_aync(). Easy to understand and to slowly transition. Caveat is the performance impact if overused. synchronicity uses a different approach - write 100% async code and expose both a sync and async interface. async def foo() becomes def foo() and async def foo.aio(). https://github.com/django/asgiref https://github.com/modal-labs/synchronicity

FastAPI docs, case when you don't create an async route > When you declare a path operation function with normal def instead of async def, it is run in an external threadpool that is then awaited, instead of being called directly (as it would block the server). https://fastapi.tiangolo.com/async/#path-operation-functions OP either meant this, or its variation, such as async_to_sync and sync_to_async. https://github.com/django/asgiref/blob/main/asgiref/sync.py Ofc this is a python example. I have no idea how it works in different languages.

ASGI > Implementations > Servers: https://asgi.readthedocs.io/en/latest/implementations.html#s... ; Daphne, Uvicorn, Hypercorn, Granian, NGINX Unit asgiref: https://github.com/django/asgiref/blob/main/asgiref/sync.py AsyncToSync, SyncToAsync a2wsgi: https://github.com/abersheeran/a2wsgi

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://github.com/django/asgiref#synchronous-code--threads. [2] https://github.com/django/asgiref/blob/main/asgiref/sync.py#...

> Django isn't independent, depends on lot many packages It is quite independent. There are between two and four dependencies: asgiref, sqlparse, tzdata on Windows only [0], and typing_extensions on <3.11 [1]. There are some optional dependencies (argon2-cffi, bcrypt, and a database library like psycopg2), but they are small and mostly self-contained. [0] https://github.com/django/django/blob/main/setup.cfg#L39-L42 [1] https://github.com/django/asgiref/blob/main/setup.cfg#L34-L3...

there is ASGI https://github.com/django/asgiref/blob/master/specs/asgi.rst but i am not sure how broadly as a common spec this has been accepted.