#12257: 1.0*pi should *not* be pi
-------------------------+-------------------------------------------------
Reporter: was | Owner: burcin
Type: | Status: needs_review
defect | Milestone: sage-6.7
Priority: minor | Resolution:
Component: | Merged in:
calculus | Reviewers:
Keywords: pynac | Work issues:
Authors: Ralf | Commit:
Stephan | 31afae4c1e4e823322795150c65dfce27df18828
Report Upstream: N/A | Stopgaps:
Branch: |
u/rws/12257 |
Dependencies: |
#18088, #18362 |
-------------------------+-------------------------------------------------
Comment (by kcrisman):
> It should be that sin(1.0*pi) returns 0.0. We can fix this somehow.
I'm not worried about printing.
Even without this patch, we now get (thanks to Pynac upgrade
{{{
sage: sin(1.0*pi)
sin(1.00000000000000*pi)
}}}
which is perhaps also not ideal, if we wanted `0.00000000000` as in the
original intent (I guess) of this ticket. So while I agree that one bug
is fixed, perhaps this could be repurposed for that - unless we want to
say that `sin(1.0*pi)` is not exact so we don't actually know it's `0.0`,
but I feel we don't do that with other things. For instance, even after
the Pynac upgrade in #18362, we have
{{{
sage: sin(0.0*pi)
0
}}}
which is really what is at issue here, I guess.
--
Ticket URL: <http://trac.sagemath.org/ticket/12257#comment:19>
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.
