Le samedi 26 mai, Dima Pasechnik a écrit:
> On 2012-05-26, Julien Puydt <julien.pu...@laposte.net> wrote:
> > Le dimanche 20 mai, Julien Puydt a écrit:
> >> sage -t --long -force_lib
> >> devel/sage/sage/interfaces/maxima_abstract.py
> >> **********************************************************************
> >> File
> >> "/home/jpuydt/sage-5.0/devel/sage-main/sage/interfaces/maxima_abstract.py",
> >> line 1595: sage: float(maxima("1.7e+17")) Expected: 1.7e+17
> >> Got:
> >> 1.6999999999999997e+17
> >> **********************************************************************
> >>
> >> This is an ECL bug, reported upstream :
> >> http://sourceforge.net/tracker/?func=detail&atid=398053&aid=3495303&group_id=30035
> >
> > Sigh... upstream tested and found it wasn't their fault, so I guess
> > there's something else somewhere :-/
>
> Can you reproduce this on Maxima console?
I tried to enter "1.7e17;" in "./sage -maxima" with sage-5.0 both on my
ARM box and on sage.math.washington.edu, and I get a difference : on
ARM, 1.69...9e+17 is returned where sage.math has 1.7e+17.
> If yes, I'd have tried installing Maxima in another lisp,
> and check if the bug is still there.
Perhaps I should contact maxima upstream?
Snark on #sagemath
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
