#17700: wrong symbolic results in case the answer is not known
--------------------------------+------------------------
Reporter: jakobkroeker | Owner:
Type: defect | Status: new
Priority: critical | Milestone: sage-6.5
Component: symbolics | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps: todo
--------------------------------+------------------------
Comment (by eviatarbach):
Thanks for opening this ticket! I think this is a huge problem in Sage
symbolics.
I can't remember what I did to change the behaviour so that when a
comparison is made and the result can't be determined it raises an
exception instead of returning `False`; I'll try to look into it this
weekend.
I like the idea of having a three-valued logic
(https://en.wikipedia.org/wiki/Three-valued_logic); unfortunately Python
makes this very difficult, as the `Tristate` class shows. There does not
seem to be an elegant solution, so I wonder if it's not just best to stick
with exceptions.
--
Ticket URL: <http://trac.sagemath.org/ticket/17700#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.
