#31515: Django tries to reuse MySQL connections that have gone away with ASGI.
---------------------------------+------------------------------------
Reporter: Braunson | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 3.0
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Changes (by felixxm):
* component: Database layer (models, ORM) => Documentation
* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
Comment:
Django 3.0 supports ASGI, however it can be really tricky to backport a
fix from master. There is a big risk of introducing new regressions, so
IMO we should document this limitation in Django 3.0.
I will try to add a proper regression test.
--
Ticket URL: <https://code.djangoproject.com/ticket/31515#comment:18>
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.b7f47fc857e1d0dad37c7e6a2585a2d2%40djangoproject.com.
