Thanks Alex and matehat, Concerning this issue of mine, I've decided to remove the images and save the objects without the ImagingCore in them, which fixed the whole thing.
On a different note, other than actively testing data which we want to put into sessions before we design the application for pickability, are there any best practices which we can adhere to concerning sessions? i.e keeping in mind to make sure data in sessions are all simple types etc. - i On Apr 12, 10:42 pm, matehat <mathieu.damo...@gmail.com> wrote: > As Alex pointed out, only picklable data can be put in the session. If > you really need that ImagingCore object in the session, you have to > make it somehow picklable by adding "__getstate__" and "__setstate__" > method for picklability (seehttp://docs.python.org/library/pickle.html). > Basically, you'd need to find out what data identifies the object as > it is now (the image path for example) so that it can be constructed > back from scratch into its current state from that data alone, which > must in turn by picklable. > > Of course if the ImagingCore class is not one of your own, you'll have > to inspect then subclass it. --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
