I just bought a new laptop, and I'm having driver troubles. I'll test it if
you make it.
On Fri, Sep 5, 2008 at 2:55 PM, Jason Grout <[EMAIL PROTECTED]>wrote:
>
> Does anyone have an already-built virtualbox image of sage?
>
> If not, is there interest? I'm building one right now.
>
> Thanks,
>
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.
>
On Sat, Sep 6, 2008 at 9:31 PM, Bill Page wrote:
>>
>> #4028: Mike Hansen: doctest and improve sage/interfaces/axiom.py
>> [Reviewed by Michael Abshoff]
>
> I have looked carefully at the changes to 'axiom.py' by Mike Hansen
> and I think there is a serious problem: The change relating to
> displa
On Tue, Sep 2, 2008 at 9:06 AM, mabshoff wrote:
>
> So expect rc0 with hopefully most of the above fixed. It has been
> a little over 2 weeks since 3.1.1, so we need to get this release
> out of the door.
>
> Sources and a sage.math only binary is in
>
> http://sage.math.washington.edu/home/mabsho
On Sep 6, 3:48 pm, Andrzej Giniewicz <[EMAIL PROTECTED]> wrote:
> Hi,
Hi,
> RPy2 is almost out -
Any idea about the timeframe?
> it would have lots of useful stuff from user view
> (data frames, formulas, works better with newer R versions) but also
> from interface view (I've heard that the
On Sep 6, 6:15 pm, "Dr. David Kirkby" <[EMAIL PROTECTED]> wrote:
> On 7 Sep, 01:35, mabshoff <[EMAIL PROTECTED]> wrote:
> > Hmm, this does not look familiar, but we used to have a gcc 4.3.1
> > patch that has been allegedly merged upstream. I am using gcc 4.2.4 on
> > Solaris at the moment an
Oh yeah, my shortlist for 3.1.2.final:
#3476: save timeit information with sage -t -timeit
#3711: notebook -- folder of worksheets not properly saved
#3918: notebook -- MAJOR BUG involving uploading file from URL
#3957: notebook -- major bug in opening notebooks and plots
#4055: serious bug in p
On 7 Sep, 01:35, mabshoff <[EMAIL PROTECTED]> wrote:
> On Sep 6, 5:18 pm, "Dr. David Kirkby" <[EMAIL PROTECTED]> wrote:
> > sage-3.1.2.alpha4/local/include/python2.5 -c ttconv/pprdrv_tt2.cpp -o
> > build/temp.solaris-2.10-sun4u-2.5/ttconv/pprdrv_tt2.o
> > cc1plus: warning: command line option "
Oops,
this took a while longer than planned, but here it is. #3984 is still
unresolved and I spend way too much time not being able to fix that
segfault on Itanium. Plenty of fixes and all but the ATLAS updates are
in. The sources and binaries are in the usual place:
http://sage.math.washington.
On Sep 6, 5:18 pm, "Dr. David Kirkby" <[EMAIL PROTECTED]> wrote:
> On 7 Sep, 00:46, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > On Sep 6, 4:30 pm, "Dr. David Kirkby" <[EMAIL PROTECTED]> wrote:
>
> > Hi Dave,
>
> Hi Micheal
>
>
>
> > > I noticed there were some Solaris fixes, so I thought I'd try a
On 7 Sep, 00:46, mabshoff <[EMAIL PROTECTED]> wrote:
> On Sep 6, 4:30 pm, "Dr. David Kirkby" <[EMAIL PROTECTED]> wrote:
>
> Hi Dave,
Hi Micheal
>
> > I noticed there were some Solaris fixes, so I thought I'd try and
> > report. Basically 'matplotlib' fails to build, as one of its
> > dependenc
On Sep 6, 4:30 pm, "Dr. David Kirkby" <[EMAIL PROTECTED]> wrote:
> On 2 Sep, 14:06, mabshoff <[EMAIL PROTECTED]> wrote:
>
> > 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
On 2 Sep, 14:06, mabshoff <[EMAIL PROTECTED]> wrote:
> 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 s
On Sep 6, 4:02 pm, "Arnaud Bergeron" <[EMAIL PROTECTED]> wrote:
> 2008/9/6 mabshoff <[EMAIL PROTECTED]>:
>
>
>
>
>
> > On Sep 6, 12:02 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> >> Dear Arnaud,
>
> > Hi,
>
> >> This is really a sage building issue so should be taken to
> >> sage-support or
2008/9/6 mabshoff <[EMAIL PROTECTED]>:
>
>
>
> On Sep 6, 12:02 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
>> Dear Arnaud,
>
> Hi,
>
>> This is really a sage building issue so should be taken to
>> sage-support or sage-devel.
>>
>> As it happens I think that the change you suggest is already par
Hi,
RPy2 is almost out - it would have lots of useful stuff from user view
(data frames, formulas, works better with newer R versions) but also
from interface view (I've heard that there will be "major memory
refresh" with about half of it used for Python/R objects and also
environments allowing
On Sep 6, 12:02 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Dear Arnaud,
Hi,
> This is really a sage building issue so should be taken to
> sage-support or sage-devel.
>
> As it happens I think that the change you suggest is already part of
> one of the patches athttp://trac.sagemath.org/s
Dear Arnaud,
This is really a sage building issue so should be taken to
sage-support or sage-devel.
As it happens I think that the change you suggest is already part of
one of the patches at http://trac.sagemath.org/sage_trac/ticket/3358
(the *ungnu* one), so if you want to get this change incor
On Sat, Sep 6, 2008 at 9:22 AM, Martin Albrecht wrote:
>
>> >> sage: axiom(maxima('1/2'))
>> >> 1
>> >> -
>> >> 2
>> >> sage: maxima(axiom('1/2'))
>> >> -1
>> > The only reason these examples work is by chance. The current
>> > code was not designed to work this way, and this approach would
>>
> >> sage: axiom(maxima('1/2'))
> >> 1
> >> -
> >> 2
> >> sage: maxima(axiom('1/2'))
> >> -1
> > The only reason these examples work is by chance. The current
> > code was not designed to work this way, and this approach would
> > only work in general for the simplest of examples (such as inte
On Sat, Sep 6, 2008 at 12:40 AM, Mike Hansen wrote:
>
> Hello,
>
>> I think it is not so bad since by defining the function float
>> appropriately this can easily parse this into a Sage floating point.
>> If this really is inconvenient then the
>>
>>> The linear representation of the object is muc
That's great, Alex, I also spent a lot of yesterday looking at the
same code. I look forward to seeing your patch and will test it on
both 32 and 64 bit machines.
John
2008/9/5 William Stein <[EMAIL PROTECTED]>:
>
> On Fri, Sep 5, 2008 at 2:48 PM, John Cremona <[EMAIL PROTECTED]> wrote:
>>
>> 2
Hi John,
I am about to put up a patch at #4064 (I'm adding a couple more doctests). It
is not perfect (it does not have proper doctests for 64 bit machines since I
don't have access to one), but I hope we can make it work soon.
Basically, I spent two days reading the libs/pari code and despairi
26 matches
Mail list logo
