#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
---------------------------------+------------------------------------
Comment (by Braunson):
Replying to [comment:22 Andrew Godwin]:
> Wait, how are you able to use async third party libraries in Django 3.0?
While it has ASGI support, that's only to run in synchronous mode; if
you're doing your own async stuff from Django views you want to be careful
or you can cause issues like this.
Using the @async_to_sync decorators for some functions where awaits might
be required
--
Ticket URL: <https://code.djangoproject.com/ticket/31515#comment:23>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.1660c4023a45d0b8e0928eb58be80c69%40djangoproject.com.
