On Monday, May 4, 2015 at 5:18:35 AM UTC-7, Nathann Cohen wrote: > > Yo ! > > > I guess it would be simpler to use __setstate__() in your use case. > > What is the difference between setstate and a helper function ? O_o >
You should probably view the initial creation (whether it's a class constructor or a helper function) as roughly equivalent to __new__ and treat __setstate__ as __init__, although the split is not quite equivalent. In the pickling process these two phases need to be split (and get split in slightly different ways) because of circular references: they can only be introduced by __setstate__. For safety against reference cycles, you should do most of your work during __setstate__, because reconstructing cycles might not give you an error during unpickling, but malformed objects instead. On the other hand, if your object might get used as a key during `__setstate__` in reference cycles, then it must be able to hash and compare before its __setstate__ executes. -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
