As you already noted on the #15207, pickling the hash will create random and impossible-to-predict unpickling failures depending on whether there happens to be a hash table collision or not.
Also, it is perfectly legal to feed values that are not constant across sessions into the hash. E.g. id(self.parent()). On Tuesday, November 19, 2013 8:43:28 PM UTC-5, Nils Bruin wrote: > > See http://trac.sagemath.org/ticket/15207 in particular. I have posted > one approach there that would probably help out in this particular > situation by pickling hash values and reinstating them early, but as I > point out there, it's fragile and not a real solution to the problem. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
