#20537: `request_finished` signal not being called with Django 1.5 and uWSGI <
1.2.6(?)
-------------------------------------+-------------------------------------
Reporter: jaap3 | Owner: jaap3
Type: Bug | Status: assigned
Component: Documentation | Version: 1.5
Severity: Normal | Resolution:
Keywords: uwsgi postgres | Triage Stage: Accepted
mysql idle connections | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Changes (by jaap3):
* has_patch: 0 => 1
* easy: 0 => 1
Comment:
I've struggled a bit as well, but I think I've hit the mark in
[https://github.com/django/django/pull/1238 this pull request].
I've folded the note in the signals page under the "Changed in Django 1.5"
as both of those were trying to say the same thing.
--
Ticket URL: <https://code.djangoproject.com/ticket/20537#comment:6>
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.d5bdd64bd91bf0f7ed12cb842f0da6a8%40djangoproject.com?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
