Updates:
Status: Fixed
Comment #4 on issue 3045 by smi...@gmail.com: float-based operations lose
precision
http://code.google.com/p/sympy/issues/detail?id=3045
(No comment was entered for this change.)
--
You received this message because you are subscribed to the Google Groups
Updates:
Labels: -EasyToFix NeedsReview smichr
Comment #3 on issue 3045 by smi...@gmail.com: float-based operations lose
precision
http://code.google.com/p/sympy/issues/detail?id=3045
`float(e)` meant applying the python function float to some arbitrary
expression, e
The `` is
Updates:
Labels: WrongResult EasyToFix
Comment #1 on issue 3045 by ronan.l...@gmail.com: float-based operations
lose precision
http://code.google.com/p/sympy/issues/detail?id=3045
Oops, that's bad! Doing the right thing in Rational.__int__ seems trivial
(i.e. just return
Comment #2 on issue 3045 by march...@kb.csu.ru: float-based operations lose
precision
http://code.google.com/p/sympy/issues/detail?id=3045
Hi, I want start working on this issue.
Could someone explain me that means `float(e)` and
n
6172839450617283945/17
Thanks.
--
You received this
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 3045 by smi...@gmail.com: float-based operations lose precision
http://code.google.com/p/sympy/issues/detail?id=3045
Although we might expect float(e) to give only 15 digits of precision,
should we expect the same from
