I really don't see the problem. On 7 Okt., 22:21, Simon King <simon.k...@uni-jena.de> wrote: > So, why shouldn't parent_class rely on the generic pickling of a > dynamic class? Well, I guess I should simply try and look how it blows > up...
I simply dropped the reduction data from the definition of a parent_class and element_class. Sage started, and now I get sage: Algebras(GF(3)).parent_class is Algebras(GF(5)).parent_class True sage: loads(dumps(Algebras(GF(3)).parent_class)) is Algebras(GF(5)).parent_class True sage: Algebras(GF(3)).parent_class is Algebras(ZZ).parent_class False There is a "todo" mentioned shortly below line 240 in category.py. That would be fixed as well: sage: Coalgebras(QQ).parent_class is Coalgebras(FractionField(QQ[x])).parent_class True So, it seems that it just works. How did the pickling problem occur? Cheers, Simon -- You received this message because you are subscribed to the Google Groups "sage-combinat-devel" group. To post to this group, send email to sage-combinat-devel@googlegroups.com. To unsubscribe from this group, send email to sage-combinat-devel+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sage-combinat-devel?hl=en.
