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 <[EMAIL PROTECTED]> wrote: > 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.__dict__.update(kwargs) > TypeError: descriptor '__dict__' for 'Empty' objects doesn't apply to > 'Query' object > > The problem appears to be due to the magic that function does of > changing the runtime class of an object. > > I was using a Psyco middleware (from the wiki, using psyco.full()). > > Just thought I'd give people a heads-up. Is psyco+Django dead? > > -Ken > > PS - The reason this didn't go through the error handling for me is > that I have a module-level model object retrieved from the database at > import time. Bad idea for a number of reasons, so it's gone in my > devel branch. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
