Fixed now.
See
https://groups.google.com/forum/?fromgroups=#!topic/django-users/FxTD5M0x-G8
for the resolution, if anyone runs into the same thing.
On Wednesday, April 10, 2013 5:04:58 PM UTC-7, Lewis Sobotkiewicz wrote:
>
> Seems to be caused by Django not sending the "reque
/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_finis
Seems to be caused by Django not sending the "request_finished" signal,
which is also bizarre, unexpected behaviour.
On Wednesday, April 10, 2013 11:47:52 AM UTC-7, Lewis Sobotkiewicz wrote:
>
> Thanks, but I'm not using the Django development version. Apparently
>
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
are released after the request, as expected.
On Wednesday, April 10, 2013 2:24:05 AM UTC-7, Andrey Kostakov wrote:
>
> https://docs.djangoproject.com/en/dev/ref/databases/#persistent-connections
>
> On Wed, Apr 10, 2013 at 2:59 AM, Lewis Sobotkiewicz
> <le...@semadic.com>
Hi all,
I'm seeing some strange, undocumented behaviour when upgtrading to Django
1.5.1. I notice that it is holding onto MySQL connections after request
processing completes, where Django 1.4.5 disconnected after every request.
Any idea what could be happening? Thanks!
--
You received this
6 matches
Mail list logo
