#13501: Fix two bugs in sage.misc.c3's implementation of the algorithm C3
-------------------------------------------------+--------------------------
Reporter: nthiery | Owner:
Type: defect | Status: needs_work
Priority: major | Milestone: sage-5.4
Component: categories | Resolution:
Keywords: method resolution order | Work issues:
Report Upstream: N/A | Reviewers: Simon King
Authors: Nicolas M. Thiéry, Simon King | Merged in:
Dependencies: | Stopgaps:
-------------------------------------------------+--------------------------
Comment (by SimonKing):
Replying to [comment:32 jdemeyer]:
> I'm getting a long doctest error:
> {{{
> sage: class A(B, C): pass
> Expected:
> Traceback (most recent call last):
> ...
> TypeError: Error when calling the metaclass bases
> Cannot create a consistent method resolution
> order (MRO) for bases B, C
> Got:
> }}}
But that's pure Python, and unrelated with our implementation of C3!
Could it be that the error message randomly choses between "Cannot create
... for bases B, C" and "Cannot create ... for bases C, B"?
If that is the case, I suggest to change the expected error message into
"Cannot create a consistent method resolution order (MRO) for bases ..."
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13501#comment:33>
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.
