#36863: Under WSGI, multiple calls to asgiref.sync.async_to_sync within the same
request do not share the same event loop.
-------------------------------------+-------------------------------------
Reporter: Mykhailo Havelia | Owner: Vishy
Type: | Algo
Cleanup/optimization | Status: new
Component: HTTP handling | Version: 6.0
Severity: Normal | Resolution:
Keywords: async, wsgi | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
Double-checked with the Steering Council:
- the reference I found to DEP 0009 is indeed out of date, we should not
draw the conclusion from that that it's accepted to add a single event
loop for WSGI handler
- the `django-async-backend` can be advanced and tested on ASGI-only
setups, including for development Daphne's runserver command, among other
options
- otherwise you can use a reverse proxy to direct traffic between WSGI and
ASGI servers
- It is possible we would revisit this once the Django ecosystem becomes
more interested in (& compatible with) free-threading Python builds
So Someday/Maybe feels appropriate for now.
--
Ticket URL: <https://code.djangoproject.com/ticket/36863#comment:16>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019c1eeb06a8-0993a7ec-27db-4eb8-93e6-e717f0f0a5a8-000000%40eu-central-1.amazonses.com.
