#11943: The category graph should comply with Python's method resolution order
---------------------------------------------------------------+------------
Reporter: SimonKing |
Owner: nthiery
Type: enhancement |
Status: needs_work
Priority: major |
Milestone: sage-4.8
Component: categories |
Keywords: category graph, method resolution order
Work_issues: Use ideas from #11900 to improve is_subcategory |
Upstream: N/A
Reviewer: |
Author: Simon King
Merged: |
Dependencies: #11900
---------------------------------------------------------------+------------
Changes (by SimonKing):
* work_issues: Rebase wrt the new version of #11900; Use ideas from
there to improve is_subcategory for
Category_singleton => Use ideas from
#11900 to improve is_subcategory
Comment:
I have updated the patch, so that (1) it applies, and (2) Sage starts. But
I'd certainly like to improve the _subcategory_hook_ by using subclass
check of parent classes. This would work generally, not only for
Category_singleton. In #11935, it would then be needed to refine the
_subcategory_hook_ for subclasses of `CategoryWithParameter`, because of
sharing parent classes.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11943#comment:51>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
