#15904: Defining __eq__ without defining __ne__ or __cmp__: sage/combinat
-------------------------------------------------+-------------------------
Reporter: darij | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.2
Component: combinatorics | Resolution:
Keywords: sage-combinat, equality, | Merged in:
inheritance | Reviewers:
Authors: | Work issues:
Report Upstream: N/A | Commit:
Branch: | Stopgaps:
Dependencies: |
-------------------------------------------------+-------------------------
Comment (by nthiery):
Thanks for investigating this! It's certainly annoying.
In principle TestSuite includes some checks about this. So it would be
interesting to see whether TestSuite was run on those failing examples.
Whenever possible, I would vote for including a trivial implementation of
__ne__ by negation of __eq__ as high up in the class hierarchy (e.g.
CombinatorialObject) to minimize the change and make it more likely for
future classes to not fall in the trap.
Cheers,
Nicolas
--
Ticket URL: <http://trac.sagemath.org/ticket/15904#comment:2>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
