#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: Rebase. Is the base() method removed? =>
Comment:
I have updated the patch.
Concerning the `base()` method for Cartesian products: If I remember
correctly, Nicolas and I agreed that it is ok to have a `base_ring()`
method for Cartesian products (meaning: If a category is defined over a
base ring then the category of Cartesian products of objects in that
category is defined over the same base ring). Thus, the patch renames the
method.
The patch should work on top of the positively reviewed patch from #11900.
Apply trac11943_mro_for_all_super_categories_lazy_hook.patch
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11943#comment:58>
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.
