#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 a "_subcategory_hook_" and document it =>
Comment:
I have added Maarten's idea of a _subcategory_hook_ and documented it. The
subcategory hook is used for `Category_over_base` (hence, it is not needed
to check for the existence of a base() attribute).
Moreover, in order to keep the generic implementation of `is_subcategory`
clean, I provided `JoinCategory` with a specialised `is_subcategory`.
The documentation looks fine to me, and all tests pass. Needs review!
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11943#comment:37>
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.
