id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
20537	`request_finished` signal not being called with Django 1.5 and uWSGI < 1.2.6(?)	Jaap Roes	Aymeric Augustin	"As discovered on the django-users mailinglist in the thread [https://groups.google.com/d/msg/django-users/FxTD5M0x-G8/rQZdOgVcDYQJ request_finished signal not being called with Django 1.5.1 with uwsgi]

The version of uWSGI in the Ubuntu/Debian apt repositories (1.0.3) doesn't call `close` on the wsgi application, this in turn causes the `request_finished` signal to never fire resulting in open database connections.

According to [http://blog.dscpl.com.au/2012/10/obligations-for-calling-close-on.html this blogpost] uWSGI >= 1.2.6 should be the first version of uWSGI that supports the expected behavior. But the same blogpost warns about other wsgi middleware potentially misbehaving.

I'm wondering why Django < 1.5 didn't show this behavior and what the best course for Django regarding this issue is.

Should there be a warning in the docs about the minimum required uWSGI version? Or should the previous behavior be restored somehow?"	Bug	closed	Documentation	1.5	Normal	fixed	uwsgi postgres mysql idle connections	Alan Justino da Silva	Ready for checkin	1	0	0	0	1	0