Since [5482], mod_python keeps a stale database connection for each HTTP request

[Ilya Semenov <semenov@…>]

Since [5482], a template is lazy-rendered. However under mod_python environment, the signal to close database connection (signals.request_finished) is sent before a template is actually rendered. If a connection is then reopened by demand during the rendering process, it will not be ever closed again and result in a stale connection, which soon overwhelms the database server.

Attached the proposed patch (sending the request_finished signal after the template is actually rendered).

Note: this can also fix #4612, though I'm not completely sure.

[Ilya Semenov <semenov@…>]

Discussion: ​http://groups.google.com/group/django-users/browse_thread/thread/588718d711a5a0f0/6124af7e3aa86773

[(removed)]

Wrap the response object, firing the signal once the response object is fully consumed

[(removed)]

If folks could kindly give that a test, would be appreciated- still preserves the iteration, but basically injects the signal firing as the last step for full iteration of the object.

At least for the mod_python wsgi implementation I looked over (and digging through pep 333), this *should* do the trick. Comments/complaints/feedback desired.

[Simon G. <dev@…>]

[5482] was backed out in [5511]