On Wed, 2008-07-02 at 04:47 -0700, Tipan wrote: > Whilst setting up a new machine for development I took down the latest > development version of Django (7825). I am now experiencing a Pickle > error when running my existing application which has been working fine > on our production servers for a few months. The error occurs when > using the Cache.set function and passing a queryset for the purposes > of caching. It also does the same in anaother view where we're passing > a queryset into the Cache.set > > I've checked the backward compatibility changes and cannot see > anything that would directly relate to it. I note that there was a fix > implented at 7773 - http://code.djangoproject.com/ticket/7506, but I'm > not sure if it is relevant. > > Has anyone encountered this recently, or can anyone shed some light on > it and suggest a work round, or does it need a ticket?
I have no idea what's going on here, although I doubt r7773 will have made things worse (since it produces less complex objects for pickling). It will help a lot if you could narrow down a rough version where this started to appear. Check out something from a while back where it worked, then checkout out something halfway in between, see if it works, etc. You could also try reducing your example code a bit to see what is the bit that is tripping the error. That might give us a few more hints. Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
