#19108: Implement Python 3 style comparison in the coercion framework
-------------------------------------+-------------------------------------
Reporter: ohanar | Owner:
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-6.9
Component: coercion | Resolution:
Keywords: | Merged in:
Authors: R. Andrew Ohana | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/ohanar/python3stylecomparison | 168fafb347a6afbdc96cae5bc27a4bea1c22f2e9
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by ohanar):
Replying to [comment:4 jdemeyer]:
> I don't understand why the `Parent` becomes involved at all. That needs
more justification.
It is for caching the partial/total order resolution. Otherwise, each time
you compare two elements, the default `_richcmp_` method would need to
determine which comparison operators are implemented by the underlying
element and then how to use those to give an answer for the requested
comparison operator.
I'm rebuilding this branch at the moment and once I'll do that I'll do
some performance tests between enabling/disabling the cache.
--
Ticket URL: <http://trac.sagemath.org/ticket/19108#comment:6>
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.
