I've added it on trac; it is ticket #15012, link [1].
[1] http://trac.sagemath.org/ticket/15012
--
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+unsubsc
On 8/6/13 8:40 AM, John Cremona wrote:
Thanks for the explanations. Are there other classes where there are
many different output representations, controlled by parameters to the
str() function istead of by setting defaults for the class?
RealNumber is another one that I patched a long time a
Thanks for the explanations. Are there other classes where there are
many different output representations, controlled by parameters to the
str() function istead of by setting defaults for the class?
John
On 6 August 2013 14:31, Jason Grout wrote:
> On 8/6/13 8:10 AM, John Cremona wrote:
>>
>>
On 8/6/13 8:10 AM, John Cremona wrote:
I really hope there is some clearer documentation than those code
comments, since I am even more confused after reading that than after
seeing the original post.
sage: a = RIF(1.332,1.334)
sage: a.center()
1.333000
sage: a
1.34?
The center is 1.33
I really hope there is some clearer documentation than those code
comments, since I am even more confused after reading that than after
seeing the original post.
sage: a = RIF(1.332,1.334)
sage: a.center()
1.333000
sage: a
1.34?
The center is 1.33 and we know that the value is "really" be
On 8/6/13 7:07 AM, Daniel Krenn wrote:
Hi,
I have the following:
sage: RIF(1.332,1.334), RIF(1.332,1.334).str(style='brackets')
(1.34?, '[1.3320 .. 1.3341]')
This is not wrong, since the questionmark means +/-1 on the previous
digit. But why is the resulting strin
