#36714: Async signals lose ContextVar state due to use of asyncio.gather
----------------------------------+------------------------------------
Reporter: Mykhailo Havelia | Owner: (none)
Type: Bug | Status: new
Component: HTTP handling | Version: dev
Severity: Normal | Resolution:
Keywords: asyncio, signals | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Carlton Gibson):
Replying to [comment:21 Mykhailo Havelia]:
Thanks for the write up Mykhailo. That's a nice example. Let me play with
it. I don't have an immediate conclusion to offer you.
> I continue to think...
The issue here is the sync handlers. If I've gone to the effort to set up
a fully asynchronous request-response flow, to then loose concurrent
signal handling for sync signal handlers that I'm not using is going to be
a pain. Can we not (at least) dispatch the async handlers concurrently,
and then handle the synchronous ones sequentially, even if the requirement
to pass the shared context here can't be worked around? 🤔
--
Ticket URL: <https://code.djangoproject.com/ticket/36714#comment:22>
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/0107019ae301da50-5dd3048b-bdff-44f7-a649-c3f4ffb93ff1-000000%40eu-central-1.amazonses.com.
