On 20 Dez., 00:47, David Roe <[email protected]> wrote: > There are certainly categories where you might want > integers to be the objects, but then I think that you need to wrap > those integers in some class inheriting from CategoryObject.
And indeed, CategoryObject does support weak references (look at sage/ structure/category_object.pxd, you will find __weakref__ defined). > Simon, where were you planning on adding this new requirement to the > documentation? Is there a good place in the Developer guide? I am pretty much sure (no time to look it up, though) that it is mentioned that the objects of a category should be derived from CategoryObject. sage.structure.element.Element is derived from SageObject, but not from CategoryObject. Hence, I think it is a bug that unwrapped elements can currently be objects of a category. However, for 11521, I'd restrict myself on fixing the memory leak and removing the problematic test. Cheers, Simon -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
