#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-5.0
Component: categories | Resolution:
Keywords: category graph, method resolution order | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Simon King | Merged in:
Dependencies: #11900, #7980 | Stopgaps:
-----------------------------------------------------------+----------------
Comment (by nthiery):
On 5.0.beta13, I was getting a random doctest failure due to the order
of the classes changing in Python's error message about MRO's:
{{{
File "/home/nthiery/sage-5.0.beta13/devel/sage-combinat/sage/misc/c3.pyx",
line 81:
sage: F.parent_class
Expected:
Traceback (most recent call last):
...
TypeError: Cannot create a consistent method resolution
order (MRO) for bases X.parent_class, Y.parent_class
Got:
Traceback (most recent call last):
... File "/home/nthiery/sage-5.0.beta13/local/bin/ncadoctest.py",
line 1231, in run_one_test
TypeError: Cannot create a consistent method resolution
order (MRO) for bases Y.parent_class, X.parent_class
}}}
The updated patch uses "..." instead of X and Y.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11943#comment:87>
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.
