Le dimanche 27 mai, Juanjo a écrit: > Your test is checking that data can be converted from python to > Maxima and viceversa. This test is built on these assumptions > > 1) The python code can convert from "double float" to Maxima's > representation accurately. > 2) Maxima can produce an accurate representation of that number > 3) The python code can recover a "double float" from Maxima's > representation.
Ah, I think I wasn't clear enough : when I wrote "maxima" in the last mail, it wasn't the "maxima()" in python/sage, but the real maxima, the software itself and not the wrapping code. Hence when I wrote that maxima() and python didn't matter -- they don't, since I don't run them at any point. I only run maxima-the-sofware on top of ECL. Compare the following : On X86_64, Maxima 5.26.0 using Lisp ECL 11.1.1 gives: (%i1) 1.7e17; (%o1) 1.7e+17 On ARM, Maxima 5.26.0 using Lisp ECL 11.1.1 gives: (%i1) 1.7e17; (%o1) 1.6999999999999998e+17 This is what the problem is about. I hope this message is less ambiguous than the previous one ; sorry for the inconvenience :-( 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
