#20537: `request_finished` signal not being called with Django 1.5 and uWSGI <
1.2.6(?)
-------------------------------------+-------------------------------------
Reporter: jaap3 | Owner: aaugustin
Type: Bug | Status: closed
Component: Documentation | Version: 1.5
Severity: Normal | Resolution: fixed
Keywords: uwsgi postgres | Triage Stage: Ready for
mysql idle connections | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Aymeric Augustin <aymeric.augustin@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"3ce1d303daa92ecb1bc3ba6344f1ec9746a79c70"]:
{{{
#!CommitTicketReference repository=""
revision="3ce1d303daa92ecb1bc3ba6344f1ec9746a79c70"
Warned that `request_finished` isn't sent by some buggy setups.
Older versions of uWSGI and Sentry's middleware do not adhere to
the WSGI spec and cause the `request_finished` signal to never
fire. Added notes to the appropriate places in the docs.
Fixed #20537.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/20537#comment:10>
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.c51f8696e4d89a8c8e357a369e112721%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
