#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:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mykhailo Havelia):
Replying to [comment:12 Jacob Walls]:
> At a glance that cleanup strategy seems more attractive
Nice, glad that direction makes sense. I'll put together an MR with tests
so we can try it out properly.
> So, am I to understand that there are, in fact, "issues" here, issues
that are not resolvable by, "just use an ASGI stack"?
I might be misunderstanding the question a bit 🙂 It does work correctly
under ASGI, yes. But I'd still consider this an issue, because the
behavior differs depending on the server stack, and that can lead to
subtle lifecycle problems especially in development where people commonly
use WSGI.
I've gotta fix this for async backends. https://github.com/Arfey/django-
async-backend/issues/4#issuecomment-3749548648
--
Ticket URL: <https://code.djangoproject.com/ticket/36863#comment:13>
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/0107019c0fadfa8d-275cff20-973d-4aae-b96e-1ba608742ba0-000000%40eu-central-1.amazonses.com.
