On Sat, May 28, 2011 at 10:50 PM, Cameron wrote:
> So I have this stack trace on my production server. I can't reproduce
> it locally and it doesn't occur with an older version of the same site
> deployed on the same server.
>
> Traceback (most recent call last):
> File "./dependencies/django/cor
Yeah no worries, I will gather as much evidence as I can and post the
details tonight. FYI I am running python 2.5.2 which comes with debian
lenny, I did not compile it myself.
And yes you are right that the wsgi server plays such a small part in
the processing of a django page. The majority of my
> As suggested on #django yesterday I swapped the site over to manage.py
> runserver and also tried gunicorn and they are both stable so it looks
> like a problem with uwsgi.
As already suggested it looks like a Python c api problem, do you mind to
fill a bug report in the uWSGI wiki with all th
As suggested on #django yesterday I swapped the site over to manage.py
runserver and also tried gunicorn and they are both stable so it looks
like a problem with uwsgi.
Gunicorn is also surprisingly fast, beating uwsgi on a httperf test to
one of the heavier pages on the site.
-
Cameron
On 29 Ma
2011/5/29 Cameron
>
>from django.conf import settings
> SystemError: ../Objects/tupleobject.c:118: bad argument to internal
> function
>
>
Seems to me as a Python bug, not something wrong in Django, so upgrading to
newer Python version may help.
--
You received this message because you are
So I have this stack trace on my production server. I can't reproduce
it locally and it doesn't occur with an older version of the same site
deployed on the same server.
Traceback (most recent call last):
File "./dependencies/django/core/handlers/wsgi.py", line 222, in
__call__
from django.c
6 matches
Mail list logo
