#19302: Stopgap for Element.__hash__
-------------------------+-------------------------------------------------
Reporter: | Owner:
ncohen | Status: needs_review
Type: | Milestone: sage-6.9
defect | Resolution:
Priority: | Merged in:
blocker | Reviewers:
Component: misc | Work issues:
Keywords: | Commit:
Authors: | bf004c2def5615b5bfe96338911d00d24f0119ac
Nathann Cohen | Stopgaps:
Report Upstream: N/A |
Branch: |
public/19302 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by ncohen):
Hello,
> I am ok with the stopgap. But I would like more consensus from
developers. The most problem I have is that it is very intrusive
Well, it pops out absolutely everywhere because this bug is very very bad,
and can generate wrong results absolutely everywhere.
> Another option, would be to move some of the commits from #19016 here
(e.g. it would at least avoid the error on polyhedron). At the same time
it will decrease the complexity of #19016 which is good. What do you
think?
I think that it would make 1000x more sense to create a new ticket
entitled "some new hash functions" (or something) and move your commits
there rather than here. Splitting #19016 into subtickets does make sense,
but I do not see a reason to merge it with this one.
Which you can also flag as 'blocker' if this is what you are after?...
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/19302#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.