#10906: lazy import can break unique representation
-----------------------+----------------------------------------------------
Reporter: nthiery | Owner: jason
Type: defect | Status: new
Priority: major | Milestone:
Component: misc | Keywords: lazy import, unique representation
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------+----------------------------------------------------
Comment(by robertwb):
Good point about categories. As for printing them out like that would make
them very unfriendly for top-level use. I could see this being a useful
flag to set for debugging though (and for a slew of other objects, so we'd
have "Gap(1)" and "Pari(1)" and "Maxima(1)" instead of just "1" for all of
them.
For our sanity, I could see rejecting lazy import objects for category
bases. It may also make sense to not delegate equality (and hashcode)
operations.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10906#comment:5>
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.
