I ran exactly into this some time ago while sanity-checking some
high-precision MPFR computations with the results of Wolfram Alpha (which
also wraps real literals into its own, I presume exact, representation).

On 3 October 2014 11:42, Volker Braun <vbraun.n...@gmail.com> wrote:

> Real literals are wrapped in their own type on the Sage command line, they
> are not hardware-floats (like in plain Python):
>
> sage: 0.001
> 0.00100000000000000
> sage: type(_)
> <type 'sage.rings.real_mpfr.RealLiteral'>
>

I am curious, why the extra zeroes in that representation in the second
line?

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to