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 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.
A general (and very conservative) rule is avoid storing "complex" Python objects in the session. Problems with being unable to marshal something (including pickling) tend to come from objects that are backed by some C-library that contains state and can't be easily pickled or from dynamically created classes. In your case, I suspect you've hit the former category, for example. If there are objects that you might want to store which you can work out how to pickle given some specifics of your situation (to pick one hypothetical: if pickling an image-like object could be done by storing a filename), I'd also recommend reading the documentation for the pickle module in the Python docs, particularly the section on pickling external objects. There are a lot of things you can do to assist standard pickling and I feel they're often under-appreciated by people using that module. Regards, 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
