#31508: ASGI Lifespan Support
-------------------------------------+-------------------------------------
Reporter: Braunson | Owner:
| Konstantin Volkov
Type: New feature | Status: closed
Component: HTTP handling | Version: 3.0
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* status: assigned => closed
* resolution: => wontfix
Comment:
Marking this as wontfix after discussion on the PR. Quoting Andrew:
> still not sure what this offers over app.ready(), so I don't think we
should take this without being really clear what it's solving and then
adding documentation that clears up when to use ready() vs lifespan
events.
Opened #32172 to track making signals async-capable.
--
Ticket URL: <https://code.djangoproject.com/ticket/31508#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 on the web visit
https://groups.google.com/d/msgid/django-updates/067.c6791d6bc9c2438de850a70972ad73c0%40djangoproject.com.
