#8860: incoherent types for real numbers
--------------------------------+-------------------------------------------
Reporter: zimmerma | Owner: AlexGhitza
Type: defect | Status: new
Priority: minor | Milestone:
Component: basic arithmetic | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
--------------------------------+-------------------------------------------
Comment(by zimmerma):
Jason,
> The docstring for RealLiteral? indicates...
how do you get this docstring?
{{{
sage: RealLiteral?
Object `RealLiteral` not found.
}}}
Anyway, I find it quite disturbing from the user point-of-view to see this
"preparsing" side-effect:
{{{
sage: type(n(1.2,prec=52))
<type 'sage.rings.real_mpfr.RealNumber'>
sage: type(n(1.2,prec=53))
<type 'sage.rings.real_mpfr.RealLiteral'>
sage: type(n(1.2,prec=54))
<type 'sage.rings.real_mpfr.RealNumber'>
}}}
> side question: ...
I forwarded the question to Francois Maltey. I guess he wants to check for
a f-p number, and
probably a python float should also return True.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8860#comment:2>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
