#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: | 39f4d3cf9c82bc17097eb761e80a4033cc38148f
Nathann Cohen | Stopgaps:
Report Upstream: N/A |
Branch: |
public/19302 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by ncohen):
> Besides, we *do* tell users:
>
> http://doc.sagemath.org/html/en/developer/coding_in_python.html#the-
hash-special-method
It's funny how we have to explain everything in docstrings or users get it
wrong, and on the other hand we expect to figure out hash issues by
themselves while browsing the developer's manual. Bullshit.
> Maybe not in the most easily accessible place, but I feel like I've been
aware of this ever since I started using Sage.
You are a developer. As William for the developers/users ratio.
> Anyway: yes, something should be fixed, but no, I don't think it's
urgent enough to print disconcerting warnings that make people think Sage
is broken.
WTF. Sage *IS* broken. Don't you get it? Having to display a stopgap is a
very bad thing, because it worries users, and what we have to do against
it is not hide the stopgaps but FIX THE BUGS.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/19302#comment:21>
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.
