On Tue, 2008-02-12 at 13:40 -0800, [EMAIL PROTECTED] wrote: > I gave locmem a quick whirl, and it blew up too. At least it returned > an error on the external page: > Mod_python error: "PythonHandler django.core.handlers.modpython" > > Traceback (most recent call last): [...] > > TypeError: object.__new__(listiterator) is not safe, use > listiterator.__new__()
Oh, crap. This sort of traceback makes me seriously consider moving to Nepal and living out the rest of my life as a mountain goat. I just know it's going to be unpleasant. Okay, for a start, what version of Django are you using? That might be important. Secondly, what are you trying to cache at the time the exception is raised? Can you work that out? Perhaps drop some debugging printing into django/core/cache/backends/locmem.py around line 23 and print out what self._cache[key] and key are at that point. We're trying to deepcopy something that doesn't handle deep-copying. The two possible solutions are to fix how we're doing the copy or detect the problem further in advance and don't try to cache that stuff. Not all objects are cachable, for technical reasons having to do with how the cache is implemented and fixing one edge case usually breaks something else. So I'd like to try and understand what's going wrong here before trying to guess what might need to be fixed. Regards, Malcolm -- Depression is merely anger without enthusiasm. http://www.pointy-stick.com/blog/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
