> As many of us have stated on IRC and elsewhere, lots of us reviewing > the categories stuff got burned out after Sage days and then busy > with lots of other stuff. There's lots of good code here that should > go in, and it's a blocker for much of the sage-combinat stuff as well.
+1 :-) > I've just reviewed http://trac.sagemath.org/sage_trac/ticket/6110 > (pickle decorator) and put a patch up at http://trac.sagemath.org/ > sage_trac/ticket/6121 (pickle metaclass) that needs review. I will look at it. > A lot of us have reservations about shipping a modified cPickle, so > I propose we proceed by using the metaclass in Category (and > elsewhere as needed) so we can get onto the really interesting > stuff. As you see fit. But I won't have the time to handle this myself, and there will be a couple technical details to handle. Some Parents are already using a metaclass (in particular UniqueRepresentation ones), and the code need to explicitly handle the merging of the metaclasses. Look for DynamicClasscallMetaclass in sage.structure.dynamic_class for an example. Best, Nicolas -- Nicolas M. Thiéry "Isil" <nthi...@users.sf.net> http://Nicolas.Thiery.name/ --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
