[sage-devel] Re: help with save/load

2014-04-14 Thread Ben Hutz
Yes, I have done that and what appears to be happening is that the first time __setstate__ is called it is called with (parent,dict1) where parent is the projective space and dict1 is the attributes of point 1. The second time it calls __setstate__(dict1,dict2) instead of (parent,dict2). This

[sage-devel] Re: help with save/load

2014-04-14 Thread Volker Braun
To see some of the machinery you can run explain_pickle(dumps(obj)) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To pos

[sage-devel] Re: help with save/load

2014-04-13 Thread Nils Bruin
On Thursday, April 10, 2014 9:38:36 AM UTC-7, Ben Hutz wrote: > > Well I'm getting closer. When loads is called on a list containing 2 > (distinct) points the first loads does fine, the second point __setstate__ > is called with just the dict instead of (parent,dict). If it is say, 2 > distinct

[sage-devel] Re: help with save/load

2014-04-10 Thread Ben Hutz
Well I'm getting closer. When loads is called on a list containing 2 (distinct) points the first loads does fine, the second point __setstate__ is called with just the dict instead of (parent,dict). If it is say, 2 distinct functions with the same parent, it works correctly (both called with (p