We've had periodic problems using Pyscho and have resorted to just
enabling it for the few key functions that really need it. In our case
there are a couple functions that do significant number crunching and
so it makes sense to Psycho them but not the rest of the site.
On Apr 29, 12:35 pm, Ken <
I just updated my production site to latest trunk, and got hard 500
errors (not even going through the exception handler). Problem caused
by bad interaction of new Query objects and psyco. Disable psyco.
The exception was:
File "/csc/django/db/models/sql/query.py", line 185, in clone
obj.__
2 matches
Mail list logo