#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: Rebase. Is the base() method removed? | Upstream: N/A
Reviewer: | Author: Simon
King
Merged: | Dependencies: #11900
-----------------------------------------------------+----------------------
Changes (by SimonKing):
* status: needs_review => needs_work
* work_issues: Is the base() method removed? => Rebase. Is the base()
method removed?
Comment:
Replying to [comment:55 jdemeyer]:
> How close is this ticket to being finished? Since #9138, #11900 and
#11943 are related, I am thinking about merging them all together. Do you
think this is a good idea?
''If'' this ticket is close to being finished, then merging the three
together would be a good idea. I am not sure how much work needs to be
done, in particular since Nicolas seems to have problems building
sage-4.8.alpha3.
Anyway, it does need work since a couple of hunks do not apply when
starting with sage-4.8.alpha3 and applying the latest patch version from
#11900 (namely the one that does not use Category_singleton for Finite*,
which Nicolas seems to prefer).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11943#comment:56>
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.
