Re: UnpickleableError when sessions are saved

On Mon, 2009-04-13 at 01:39 -0700, Iqbal Abdullah wrote: > 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

Re: UnpickleableError when sessions are saved

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

Re: UnpickleableError when sessions are saved

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 (see http://docs.python.org/library/pickle.html). Basically,

Re: UnpickleableError when sessions are saved

On Sat, Apr 11, 2009 at 9:45 PM, Iqbal Abdullah wrote: > > Hi guys, > > In one of our views, we're getting the error below: > > Traceback (most recent call last): > File "/usr/lib/python2.5/site-packages/django/core/servers/ > basehttp.py", line 278, in run >self.result

UnpickleableError when sessions are saved

Hi guys, In one of our views, we're getting the error below: Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/django/core/servers/ basehttp.py", line 278, in run self.result = application(self.environ, self.start_response) File