On Jan 27, 3:00 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Jan 26, 2008 11:46 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > mabshoff wrote:
> > > On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> > > dortmund.de> wrote:
> > >> 2.10.1.alpha2 turned out to be a disaster to put
On Jan 26, 2008 11:46 AM, Jaap Spies <[EMAIL PROTECTED]> wrote:
>
> mabshoff wrote:
> > On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> > dortmund.de> wrote:
> >> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
> >> the rc0 que at
> >>
> >> http://sage.math.washington.edu/
mabshoff wrote:
>
>
> On Jan 26, 11:29 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
>> mabshoff wrote:
>>> On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
>>> dortmund.de> wrote:
2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
the rc0 que at
http://sage.math.wa
On Jan 26, 11:29 pm, Jaap Spies <[EMAIL PROTECTED]> wrote:
> mabshoff wrote:
> > On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> > dortmund.de> wrote:
> >> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
> >> the rc0 que at
>
> >>http://sage.math.washington.edu/home/mabs
On Jan 26, 11:14 pm, Robert Bradshaw <[EMAIL PROTECTED]>
wrote:
> R Build fail on OS X (10.4, intel)
>
Hi Robert,
I will be checking into this, but it will be a while until I will
finish my OSX build.
Cheers,
Michael
--~--~-~--~~~---~--~~
To post to this group
mabshoff wrote:
> On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> dortmund.de> wrote:
>> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
>> the rc0 que at
>>
>> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/rc0/
>>
>> rc0 should be out sooner rather
R Build fail on OS X (10.4, intel)
On Jan 26, 2008, at 11:46 AM, Jaap Spies wrote:
>
> mabshoff wrote:
>> On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
>> dortmund.de> wrote:
>>> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check
>>> out
>>> the rc0 que at
>>>
>>> http://sag
I believe the point of is_simplified() is to see if the result has
already been simplified. Trying to detect if simplify() will modify
self is a (potentially) expensive operation, so if it knows it's been
simplified then it returns True, but otherwise it returns False
(which may be a false
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
The following is a bit confusing:
sage: f=(x-1)
sage: f.is_simplified()
False
sage: g=f.simplify()
sage: g
x - 1
sage: g.is_simplified()
True
Is this on purpose? I.e. if one had to describe what the function
is_simplified() is supposed to do,
mabshoff wrote:
> On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> dortmund.de> wrote:
>> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
>> the rc0 que at
>>
>> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/rc0/
>>
>> rc0 should be out sooner rather t
mabshoff wrote:
> On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
> dortmund.de> wrote:
>> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
>> the rc0 que at
>>
>> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/rc0/
>>
>> rc0 should be out sooner rather t
On Jan 26, 4:38 pm, Simon King <[EMAIL PROTECTED]> wrote:
> Dear Michael,
>
> > Yep, please do so
>
> Done. Seehttp://trac.sagemath.org/sage_trac/ticket/1940
>
> I didn't know whom to assign to, and i hope that my choices ("major"
> and "milestone sage.2.10.1") are ok.
Yep. Since you did pick the
Dear Michael,
> Yep, please do so
Done. See http://trac.sagemath.org/sage_trac/ticket/1940
I didn't know whom to assign to, and i hope that my choices ("major"
and "milestone sage.2.10.1") are ok.
Yours
Simon
--~--~-~--~~~---~--~~
To post to this group, sen
On Jan 26, 4:05 pm, Simon King <[EMAIL PROTECTED]> wrote:
> Dear Sage developers,
Hi Simon,
> the three lines of code below produce a segmentation fault. Shall i
> open a ticket?
Yep, please do so. libSingular is not surprisingly involved:
(gdb) bt
#0
__pyx_pf_4sage_5rings_10polynomial_34mu
Dear Sage developers,
the three lines of code below produce a segmentation fault. Shall i
open a ticket?
Yours
Simon
--
| SAGE Version 2.10, Release Date: 2008-01-18|
| Type notebook() for the GUI, a
On Jan 26, 12:31 pm, mabshoff <[EMAIL PROTECTED]
dortmund.de> wrote:
> 2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
> the rc0 que at
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/rc0/
>
> rc0 should be out sooner rather than later. If you want to
2.10.1.alpha2 turned out to be a disaster to put it mildly. Check out
the rc0 que at
http://sage.math.washington.edu/home/mabshoff/release-cycles-2.10.1/rc0/
rc0 should be out sooner rather than later. If you want to build
yourself you need the new r.spkg (p12 to be exact) and Sage-2.10.1.rc0-
e
As a general info: I broke R and rpy:
a) R is broken for parallel make. I did fix that.
b) rpy still thinks it is linking against RLapack on non-OSX, which we
no longer build there. Since the old Sage directory I also build the
new r.spkg against contained a copy of libR* in local/lib this didn'
18 matches
Mail list logo
