So what was stated on the stack overflow post that connections are somehow closed only at the end of a request through the request end signal is still the actual behavior?
Any best / suggested practices on how to handle connections on threads that are not part of the request cycle? Considering the connections are automatically opened for you, it would be great for them to be automatically closed/disposed for you on thread's death, which right now seems to happen some times, and some times not, leaking connections (something I'm trying to figure out what's going on). -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/36c63148-a6c1-44f2-b862-57a1cb750c01%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
