[sage-devel] Status update on 3.0.1.final

Hi, 3.0.1.final will not happpen tonight, i.e. Saturday. We are down to one blocker, i.e. the ring.pyx failure in Singular [#3098]. We have some patches but they need some more fine tuning. Other than that there are two pbuild tickets that might make it if patches are posted: #3097: the missing

[sage-devel] Re: Sage 3.0.1.rc0 released!

512 mb I think these are relevant part I forgot to post. --copy and paste--- sage -t devel/sage/sage/rings/polynomial/pbori.pyx ** File "/mnt/documents/sage-3.0.1.rc0/tmp/pbori.py", line 2512: sage: f(x=var('a'),y=va

[sage-devel] Re: RFC: article for OpenWetWare

Just to throw a few thoughts in, I think sage is excellently positioned to have a big impact for empiricists and theoreticians within the biological sciences as well as bio-informatics. I haven't trudged through much of openwetware yet, but it might be useful to expand/make another page that show

[sage-devel] Re: Sage 3.0.1.rc0 released!

On Sat, May 3, 2008 at 7:53 PM, elflapper <[EMAIL PROTECTED]> wrote: > > I just ran the test: > The following tests failed: > > > sage -t devel/sage/sage/rings/polynomial/pbori.pyx > sage -t devel/sage/sage/rings/complex_double.pyx > Total time for all tests: 5126.3 seconds >

[sage-devel] Re: Sage 3.0.1.rc0 released!

I just ran the test: The following tests failed: sage -t devel/sage/sage/rings/polynomial/pbori.pyx sage -t devel/sage/sage/rings/complex_double.pyx Total time for all tests: 5126.3 seconds On Archlinux x86 On May 3, 12:17 am, elflapper <[EMAIL PROTECTED]> wrote: > This build

[sage-devel] Re: Sage 3.0.1.rc0 released!

On Sat, May 3, 2008 at 1:24 PM, Willem Jan Palenstijn <[EMAIL PROTECTED]> wrote: > > On Sat, May 03, 2008 at 11:57:00AM -0700, mabshoff wrote: > > On May 3, 8:44?pm, "William Stein" <[EMAIL PROTECTED]> wrote: > > > ? ? ? ? sage -t ?devel/sage/sage/rings/ring.pyx > > > know issue. Track ticket s

[sage-devel] Re: IRIX compilation problem...

Well, as the author of eclib I hope I can help. It is a C++ library. It uses the NTL library, whcih includes a multiprecision real number type called RR. MTL does not have multiprecision complexes, so implement those using RR for the real and imaginary parts, and a standard C++ library template

[sage-devel] Re: Sage 3.0.1.rc0 released!

On Sat, May 03, 2008 at 11:57:00AM -0700, mabshoff wrote: > On May 3, 8:44?pm, "William Stein" <[EMAIL PROTECTED]> wrote: > > ? ? ? ? sage -t ?devel/sage/sage/rings/ring.pyx > know issue. Track ticket should be up shortly. Singular related. This is now #3098. It is caused by a rather subtle prob

[sage-devel] Re: Sage 3.0.1.rc0 released!

On Sat, May 3, 2008 at 11:57 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > On May 3, 8:44 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > > Build testing of sage-3.0.1.rc0: > > Hi, > > > > Powerpc OS X 10.5: > > sage -t devel/sage/sage/dsage/tests/testdoc.py > > sage -t deve

[sage-devel] Re: Sage 3.0.1.rc0 released!

On May 3, 8:44 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > Build testing of sage-3.0.1.rc0: Hi, > Powerpc OS X 10.5: >         sage -t  devel/sage/sage/dsage/tests/testdoc.py >         sage -t  devel/sage/sage/modular/abvar/abvar.py >         sage -t  devel/sage/sage/modular/abvar/homspace.

[sage-devel] Re: Sage 3.0.1.rc0 released!

Build testing of sage-3.0.1.rc0: Powerpc OS X 10.5: sage -t devel/sage/sage/dsage/tests/testdoc.py sage -t devel/sage/sage/modular/abvar/abvar.py sage -t devel/sage/sage/modular/abvar/homspace.py sage -t devel/sage/sage/server/simple/twist.py Total time for all

[sage-devel] Re: Sage 3.0.1.rc0 released!

On May 3, 4:18 pm, Alex Ghitza <[EMAIL PROTECTED]> wrote: > Built fine on Hi Alex, > Linux sillyname 2.6.22-gentoo-r5 #2 SMP Tue Aug 28 23:46:12 UTC 2007 > i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux > > Doing 'make test', got stuck at dsage/tests/testdoc.py so I had to k

[sage-devel] Re: Sage 3.0.1.rc0 released!

On May 3, 7:37 pm, "David Joyner" <[EMAIL PROTECTED]> wrote: Hi David, > Sorry. Here it ishttp://sage.math.washington.edu/home/wdj/patches/install.log > (or will be in a few minutes - it's still uploading). I think I found it: The working version of mwrank.so is compiled with g ++, while the no

[sage-devel] Re: Sage 3.0.1.rc0 released!

Built fine on Linux sillyname 2.6.22-gentoo-r5 #2 SMP Tue Aug 28 23:46:12 UTC 2007 i686 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux Doing 'make test', got stuck at dsage/tests/testdoc.py so I had to kill it. I've put the build log at http://bayes.colby.edu/~ghitza/inst

[sage-devel] Re: Sage 3.0.1.rc0 released!

On Sat, May 3, 2008 at 1:19 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On May 3, 7:14 pm, "David Joyner" <[EMAIL PROTECTED]> wrote: > > On Sat, May 3, 2008 at 12:55 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > Hi David, > > > > > Can you post a link to the build log? This is very li

[sage-devel] Re: Sage 3.0.1.rc0 released!

On May 3, 7:14 pm, "David Joyner" <[EMAIL PROTECTED]> wrote: > On Sat, May 3, 2008 at 12:55 PM, mabshoff <[EMAIL PROTECTED]> wrote: Hi David, > >  Can you post a link to the build log? This is very likely related to > >  pbuild's different linker flags. We should be able to hunt this down >

[sage-devel] Re: Sage 3.0.1.rc0 released!

On Sat, May 3, 2008 at 12:55 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > On May 3, 6:33 pm, "David Joyner" <[EMAIL PROTECTED]> wrote: > > Hi David, > > > > Possibly strange results on an ubuntu 7.10amd64 machine. (It is a > > rather old machine > > though, so many this is not something to wor

[sage-devel] Re: Sage-2.11 compilation problem under Irix

On May 3, 6:35 pm, Oskar45 <[EMAIL PROTECTED]> wrote: > Hi everyone, Hi Oskar, > am trying to get sage-2.11 running under the officially unsupported > [!!!] > Irix 6.5.30 with MipsPro 7.4.4 [my box is an SGI Fuel/R16000]. Up to > now, > after battling a few inconsistencies, I got GMP, PARI and N

[sage-devel] IRIX compilation problem...

Hi everyone, am trying to get sage-2.11 running under the officially unsupported [!!!] Irix 6.5.30 with MipsPro 7.4.4 [my box is an SGI Fuel/R16000]. Up to now, after battling a few inconsistencies, I got GMP, PARI and NTL installed. However, I now got stuck with the compilation of . As Michael h

[sage-devel] Sage-2.11 compilation problem under Irix

Hi everyone, am trying to get sage-2.11 running under the officially unsupported [!!!] Irix 6.5.30 with MipsPro 7.4.4 [my box is an SGI Fuel/R16000]. Up to now, after battling a few inconsistencies, I got GMP, PARI and NTL installed. However, I now got stuck with the compilation of . As Michael h

[sage-devel] Re: Sage 3.0.1.rc0 released!

On May 3, 6:33 pm, "David Joyner" <[EMAIL PROTECTED]> wrote: Hi David, > Possibly strange results on an ubuntu 7.10amd64 machine. (It is a > rather old machine > though, so many this is not something to worry about.) Yes, it is ;) > export SAGE_PBUILD=yes > export SAGE_BUILD_THREADS=2 > make >

[sage-devel] Re: ISSAC abstract

On May 3, 7:50 pm, root <[EMAIL PROTECTED]> wrote: > >Ok. I'll try a fedora 3 build. > > Sage failed to build in fedora 3 > > The log is at > > > Tim Hi Tim, R fails to build since it picks up the system's readline. We have some similar issue wit

[sage-devel] Re: ISSAC abstract

>>> I can try to build a Sage binary on Fedora 3 if you wish >>> but I'm not optimistic. I know that my Fedora 5 could not >>> build Sage because the compiler was too old. >> >>The compiler wasn't too old, it was *borken*, i.e. "internal compiler >>error". IIRC it was some gcc 4.1.0 and as well al

[sage-devel] Re: Sage 3.0.1.rc0 released!

Possibly strange results on an ubuntu 7.10amd64 machine. (It is a rather old machine though, so many this is not something to worry about.) export SAGE_PBUILD=yes export SAGE_BUILD_THREADS=2 make Build went fine. However, sage -testall started messing up almost immediately. Here is some of it:

[sage-devel] Re: Sage 3.0.1.rc0 released!

On May 3, 5:26 pm, Andrzej Giniewicz <[EMAIL PROTECTED]> wrote: > Hi, Hi Andrzej, > built and tested on Arch 32, only one failure (were 3 for alpha)... > same as with 3.0.0: > > sage -t  3.0.1.rc0/devel/sage/sage/rings/complex_double.pyx > **

[sage-devel] Re: Sage 3.0.1.rc0 released!

Hi, built and tested on Arch 32, only one failure (were 3 for alpha)... same as with 3.0.0: sage -t 3.0.1.rc0/devel/sage/sage/rings/complex_double.pyx ** File "/opt/sage/tmp/complex_double.py", line 1659: sage: z^2 - z + 1

[sage-devel] Re: Sage 3.0.1.rc0 released!

On May 3, 4:14 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: Hi John, > ok , I thought I should have been listening in on IRC when sage-devel > went quiet! Yes, #sage-devel is often the place to get quick answers, especially to debug problems. > This doesn't actually tell me what I should do.

[sage-devel] Re: Sage 3.0.1.rc0 released!

ok , I thought I should have been listening in on IRC when sage-devel went quiet! This doesn't actually tell me what I should do. (You were right that this is with PBUILD, by the way). But I killed the --testall. Any ideas on the 8 rogue sage processes I have goung back to April 10? In full t

[sage-devel] Re: Computing large Bernoulli numbers

I probably also mean: Then the error in the the zeta function not: Then the error in the inverse of the zeta function Bill. On 3 May, 13:12, Bill Hart <[EMAIL PROTECTED]> wrote: > I think I nearly understand what Pari does. > > The value of B_k is given by zeta(n)*(2*n!)/(2^n pi^n). However,

[sage-devel] Re: Sage 3.0.1.rc0 released!

On May 3, 3:07 pm, "John Cremona" <[EMAIL PROTECTED]> wrote: > Two successful builds of rc0 (32 and 64 bit linux).   The 64-bit one > seems to have stalled doing testall at this point: > > sage -t  devel/sage/sage/dsage/dist_functions/all.py >          [1.3 s] > sage -t  devel/sage/sage/dsage/sc

[sage-devel] Re: Sage 3.0.1.rc0 released!

All ok on my 32-bit machine: All tests passed! Total time for all tests: 4034.3 seconds Please see /home/jec/sage-3.0.1.rc0/tmp/test.log for the complete log from this test. [EMAIL PROTECTED] -a Linux fermat 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux 2008/5/3 John Crem

[sage-devel] Re: Sage 3.0.1.rc0 released!

All tests passed on my intel mac pro, running OS X 10.4.11. -M. Hampton On May 3, 8:07 am, "John Cremona" <[EMAIL PROTECTED]> wrote: > Two successful builds of rc0 (32 and 64 bit linux). The 64-bit one > seems to have stalled doing testall at this point: > > sage -t devel/sage/sage/dsage/dist

[sage-devel] Re: RFC: article for OpenWetWare

Feel free to point others to it now. I improved it (hopefully) a little bit, and I am now posting about it on my blog (which should get fed into Planet Sage). I can always change it if there are errors/ omissions. Thanks for the feedback. M. Hampton On May 2, 6:02 pm, Simon King <[EMAIL PROTE

[sage-devel] Re: Sage 3.0.1.rc0 released!

Two successful builds of rc0 (32 and 64 bit linux). The 64-bit one seems to have stalled doing testall at this point: sage -t devel/sage/sage/dsage/dist_functions/all.py [1.3 s] sage -t devel/sage/sage/dsage/scripts/nodoctest.py (skipping) -- nodoctest.py file in directory sage -t d

[sage-devel] Re: Computing large Bernoulli numbers

Sorry, this: The log of this expression is never more than 0.1 of the log of n!. should read: The log of this expression is always within 0.1 of the log of n!. Bill. On 3 May, 13:12, Bill Hart <[EMAIL PROTECTED]> wrote: > I think I nearly understand what Pari does. > > The value of B_k is giv

[sage-devel] Re: Computing large Bernoulli numbers

I think I nearly understand what Pari does. The value of B_k is given by zeta(n)*(2*n!)/(2^n pi^n). However, zeta(n) is *very* close to 1 for large n. So one starts by computing zeta to a precision given by the size of (2*n!)/(2^n pi^n) (which is basically the size of B_k) with 3 added to the pre

[sage-devel] Re: Sage 3.0.1.rc0 released!

This builds without error on Archlinux (3.0 didn't build with just 'make')!!! On May 2, 11:43 pm, mabshoff <[EMAIL PROTECTED]> wrote: > Hello, > > This is the end of the 3.0.1 release cycle. The build was  announced > in IRC about eight hours ago, but since I took a  long nap in the > meantime I

[sage-devel] Re: SAGE 3.0alpha6 Debian package issues

It turns out the singular problem was that /usr/lib/libsingular.so has to be marked as executable for Singular to load it. The LinBox problem went away when I upgraded to 3.0.1alpha1. -Tim Abbott On Apr 26, 9:28 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Apr 27, 2:57 am, T