Re: request_finished signal not being called with Django 1.5.1 with uwsgi

I'm being hit by the same issue. I don't really understand why it worked with older versions of Django though? That seems to be a bug.

Op vrijdag 12 april 2013 01:28:42 UTC+2 schreef Lewis Sobotkiewicz het volgende:

So figured it out.

Apparently Ubuntu 12.04 packages uwsgi 1.0.3 in their apt repository, which doesn't support calling close() on the WSGI application object returned by Django. I had installed that uWsgi version, then installed a more up-to-date version with pip. ie.

pip install uwsgi==1.4.4

Subsequently, running uwsgi from the command line gives the later version:

$ uwsgi --version
1.4.4

However, when starting uwsgi with /etc/init.d/uwsgi, it was using Ubuntu's older, pre-packaged version. I assumed that pip would overwrite that version. Silly me. Fixed by editing /etc/init.d/uwsgi to point DAEMON=/usr/bin/uwsgi to the version installed by pip.

On Wednesday, April 10, 2013 4:55:51 PM UTC-7, Lewis Sobotkiewicz wrote:

Hi there,

I'm noticing some strange behaviour with Django 1.5.1 and uwsgi - The builtin signal django.core.signals.request_finished isn't being triggered. I've tried various versions of uwsgi, and they all have the same behaviour.

Also, when I downgrade to Django 1.4.5, the normal behaviour resumes.

Any idea why this might be happening? It's causing my DB connections to remain open after a request.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.