#19519: Django fails to close db connections at end of request-response cycle
-------------------------------------+-------------------------------------
Reporter: amosonn@… | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Release blocker | Triage Stage: Accepted
Keywords: connection, | Needs documentation: 0
managment, closing, mysql, | Patch needs improvement: 0
innodb, signal, generator | UI/UX: 0
Has patch: 0 |
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by aaugustin):
Replying to [comment:9 apollo13]:
> Related: http://bugs.python.org/issue16220 -- We either have to raise
the required python versions or fix it in our wsgiref subclass (probably
the later since Python didn't fix it in 2.6, unless it wasn't broken which
I doubt).
This fix will be available in Python 2.7.4, which isn't released yet.
If we want to fix this by triggering `request_finished` in the WSGI
iterable's `close()` method we must ensure it's reliably closed.
I've re-opened #16241.
--
Ticket URL: <https://code.djangoproject.com/ticket/19519#comment:11>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
