Here is a better definition:
def float(x,e,b):
return RealField(axiom('precision()$Float'))(x)*b^e
On Sat, Sep 6, 2008 at 11:10 PM, Bill Page wrote:
> On Sat, Sep 6, 2008 at 10:49 PM, Bill Page wrote:
>> On Sat, Sep 6, 2008 at 10:32 PM, Mike Hansen wrote:
>>>
>>> I still find the following b
On Sat, Sep 6, 2008 at 10:49 PM, Bill Page wrote:
> On Sat, Sep 6, 2008 at 10:32 PM, Mike Hansen wrote:
>>
>> I still find the following behavior much worse than the current
>> behavior (which is why I made the change):
>>
>> sage: axiom(2.123)
>> float(156649750673941527080,-66,2)
>>
>> That's no
On Sat, Sep 6, 2008 at 10:32 PM, Mike Hansen wrote:
>
> Another data point:
> sage: str(maxima(1/2)).strip()
> '1\r\n -\r\n
> 2'
>
Oh, groan! It's bad enough that Sage rejects the Python convention
concerning repr but this is terrible. :-(
>
Hello,
> After sending this email I reviewed some of the previous messages
> about the use of repr in Sage. One way of summarizing this is that
> Sage does not actually follow the usual Python convention here (in
> spite of my examples :-).
Yes, Sage has consciously rejected that convention.
>
Hello folks,
this is alpha4 and more progress toward the final 3.1.2. As some
people have noticed this release is getting larger than the original
3.1, but I guess such is life. THe m4ri issues have been sorted out,
but there are still four major issues:
* ghmm/hmm
* gp.py doctest failing on 3
