#11943: The category graph should comply with Python's method resolution order
---------------------------+------------------------------------------------
Reporter: SimonKing | Owner: nthiery
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.8
Component: categories | Keywords: category graph, method resolution
order
Work_issues: | Upstream: N/A
Reviewer: | Author: Simon King
Merged: | Dependencies: #11900
---------------------------+------------------------------------------------
Changes (by SimonKing):
* status: needs_work => needs_review
* work_issues: Use ideas from #11900 to improve is_subcategory =>
Comment:
The patch is updated, and with it all tests should pass.
The patch uses the `_subcategory_hook_` mechanism, which will make it
easier in #11935 to cope with the case of shared parent classes. However,
for now, the default `_subcategory_hook_`, which tests whether one parent
class is subclass of the other, is actually sufficient to determine
subcategories, with the only exception of join categories.
Needs review, I'd say!
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11943#comment:52>
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.
