[sage-devel] Solaris problem when building readline - due to Darwin test in SAGE

I tried building sage 3.0 on an x86 laptop running Solaris Express Developer Edition snv_79b. At the time of writing this is the latest developer edition, but there are later community editions of Solaris. I was using gcc 4.0.2, but Sun's make program in /usr/bin/make. bash-3.2$ cat /etc/release

[sage-devel] Re: Test errors for Sage 3.0 on OS X

On Apr 24, 1:54 am, Bjake Hammersholt Roune <[EMAIL PROTECTED]> wrote: Hi Bjake, > It just now occured to me that this might be due to counting wall-time > instead of CPU-time, since I put the machine to sleep during a lecture > while it was running the tests. Ok, that explains it. On OSX tim

[sage-devel] Re: Initial support for posets

On Wed, Apr 23, 2008 at 1:42 PM, Franco Saliola <[EMAIL PROTECTED]> wrote: > > On Wed, Apr 23, 2008 at 4:05 PM, Robert Miller <[EMAIL PROTECTED]> wrote: > > > We might want to think about the naming conventions for Lattice. As > > with all words in mathematics, this one has multiple meanings.

[sage-devel] Re: Sage, Maxima, Lisp

On Apr 23, 12:08 pm, "Bill Page" <[EMAIL PROTECTED]> wrote: ... > Both you and Gaby have discussed the possibility of defining an > abstract machine (aka. run-time system) to replace the role that Lisp > plays for Axiom. We also know that Aldor has already defined such a > machine called FOAM. FOA

[sage-devel] Re: notebook features discussion

On Wed, Apr 23, 2008 at 8:29 PM, John Voight <[EMAIL PROTECTED]> wrote: > > Hello! > > I've run some Sage labs using the notebook here at UVM and two things > have come up. > > (1) At the end of class, I asked my students to print out their work > and turn it in. I stopped this almost immedi

[sage-devel] Re: small documentation problem: "\ " at the end of a line

> On Wed, 23 Apr 2008 at 01:25PM -0700, John H Palmieri wrote: > This is exactly why die-hard Python people say "don't use backslashes to > continue statements": > > http://docs.python.org/dev/howto/doanddont.html#using-backslash-to-continue-statements > > Perhaps we should link to the above gu

[sage-devel] Re: sage OSX 10.4.4 dmg

On Wed, Apr 23, 2008 at 9:28 PM, root <[EMAIL PROTECTED]> wrote: > > Have you copied the image? > Can I remove it? > Yep it's here: http://sagemath.org/SAGEbin/apple_osx/powerpc/ --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups

[sage-devel] Re: notebook features discussion

Hello! I've run some Sage labs using the notebook here at UVM and two things have come up. (1) At the end of class, I asked my students to print out their work and turn it in. I stopped this almost immediately, since the printouts are hugely wasteful: blank pages, things overrun the margins, et

[sage-devel] Re: sage OSX 10.4.4 dmg

My Mac box is generally idle except when I'm doing the every-other-month Axiom release. If you need images I can build them for OSX 10.4 Tim --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send

[sage-devel] Re: small documentation problem: "\ " at the end of a line

On Wed, 23 Apr 2008 at 09:45PM -0400, Alex Ghitza wrote: > Dan Drake wrote: > > On Wed, 23 Apr 2008 at 01:25PM -0700, John H Palmieri wrote: > > This is exactly why die-hard Python people say "don't use backslashes to > > continue statements": > > > > http://docs.python.org/dev/howto/doanddont.htm

[sage-devel] Re: sage OSX 10.4.4 dmg

Have you copied the image? Can I remove it? Tim --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/gr

[sage-devel] Re: sage OSX 10.4.4 dmg

On Wed, Apr 23, 2008 at 7:49 PM, <[EMAIL PROTECTED]> wrote: > > Here is a disk image of the vanilla Sage release for OSX 10.4.4 > > > http://daly.axiom-developer.org/sage-3.0-osx10.4-ppc-PowerMacintosh-Darwin.dmg > Thanks!! I've posted it. William --~--~-~--~~~-

[sage-devel] sage OSX 10.4.4 dmg

Here is a disk image of the vanilla Sage release for OSX 10.4.4 http://daly.axiom-developer.org/sage-3.0-osx10.4-ppc-PowerMacintosh-Darwin.dmg Tim Daly --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this

[sage-devel] Re: Readline and Solaris: Testing strings with == is not portable.

Hi, One more thing about Solaris: The game plan of the Solaris port has slightly changed. The initial port will be Solaris 10 and no longer Solaris 9. The compiler I will use is Sun Fort 12 [or whatever cc 5.9 corresponds to]. The main reason is that the header situation with Sun's compiler is mu

[sage-devel] Re: small documentation problem: "\ " at the end of a line

Dan Drake wrote: > On Wed, 23 Apr 2008 at 01:25PM -0700, John H Palmieri wrote: > This is exactly why die-hard Python people say "don't use backslashes to > continue statements": > > http://docs.python.org/dev/howto/doanddont.html#using-backslash-to-continue-statements > > Perhaps we should link

[sage-devel] Re: Readline and Solaris: Testing strings with == is not portable.

On Apr 24, 2:42 am, "Dr. David Kirkby" <[EMAIL PROTECTED]> wrote: Hi David, > I tried building sage 3.0 on an x86 laptop running Solaris Express > Developer Edition snv_79b. At the time of writing this is the latest > developer edition, but there are later community editions of Solaris. > I was

[sage-devel] Re: small documentation problem: "\ " at the end of a line

A point of clarification: AFAIK, no newlines were used originally in the tutorial or construction docs. They were introduced only to increase the readability of the pdf versions. Even as it is, in the 2008.01.18 version of the tutorial sold on lulu, there are 10 pages or so which have lines cut of

[sage-devel] Re: Sage 3.0 released

On Apr 24, 2:22 am, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 6:24 pm, mark mcclure <[EMAIL PROTECTED]> wrote: Hi Mark, > make; followed by "sage -ba" seems to have done the trick.  Everything > seems to be working great and "./sage -testall" passed all tests. > > I've got a workin

[sage-devel] enumerating colorings of graphs

Robert, this question might be mainly to you: I have a need to enumerate all possible black and white colorings of a graph, up to (colored) isomorphism. Is there a way to use some of the NICE code to make this fast? It seems like I read somewhere that Robert was going to generalize NICE to l

[sage-devel] Re: small documentation problem: "\ " at the end of a line

On Wed, 23 Apr 2008 at 01:25PM -0700, John H Palmieri wrote: > > In the section of the tutorial on 3d plotting, > > > > the continuation characters "\" all have spaces after them, which > messes up cutting and pasting. Also in the section on Maxi

[sage-devel] Re: Sage 3.0 released

On Apr 23, 6:24 pm, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 6:17 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > On Apr 24, 12:14 am, mark mcclure <[EMAIL PROTECTED]> wrote: > > > The trailing kg is missing. Should I simply change the > > > name and try again? > > > Yes.

[sage-devel] Readline and Solaris: Testing strings with == is not portable.

I tried building sage 3.0 on an x86 laptop running Solaris Express Developer Edition snv_79b. At the time of writing this is the latest developer edition, but there are later community editions of Solaris. I was using gcc 4.0.2, but Sun's make program in /usr/bin/make. bash-3.2$ /usr/sbin/psrinfo

[sage-devel] Re: Test errors for Sage 3.0 on OS X

> > sage -t devel/sage/sage/modular/abvar/morphism.py *** *** > > Error: TIMED > > OUT! *** *** > > *** *** Error: TIMED OUT! *** *** > > [1358.6 s] > > [...] > > Odd, it shouldn't time out on that machine. I am hoping William or > Craig can take a close look since they are much

[sage-devel] Re: Trouble finding the normalizer of a subgroup

AFAIK, the normalizer of a group is not yet implemented. If you type sage: s6.normalizer? you'll see the synax for that command. My guess is that normalizer_of_group would be an easy function to implement (and I can do that if no one else wants to). On Wed, Apr 23, 2008 at 4:06 PM, Hy Ginsberg <[

[sage-devel] Re: Sage 3.0 released

On Apr 23, 6:17 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > On Apr 24, 12:14 am, mark mcclure <[EMAIL PROTECTED]> wrote: > > The trailing kg is missing. Should I simply change the > > name and try again? > > Yes. Run make, then a "sage -b". If Sage starts up all ought be be > fixed. If

[sage-devel] Re: Sage 3.0 released

On Apr 24, 12:14 am, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 6:10 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > for whatever reason there is no Singular in your build log. Right at > > the top it says: > > ... > > Could you check if spkg/standard contains any file call

[sage-devel] Re: Sage 3.0 released

On Apr 23, 6:10 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > for whatever reason there is no Singular in your build log. Right at > the top it says: > ... > Could you check if spkg/standard contains any file called > singular-3-0-4-2-20080405.p1.spkg, i.e: No, there's not. Strangely, th

[sage-devel] Re: [fricas-devel] Re: [sage-devel] Re: FriCAS/Open-Axiom and SAGE

Yes, both books are part of the documentation that ships with Axiom. The Jenks book (ISBN 0-387-97855-0) is in src/doc/book.pamphlet (the latex sources). It is also available as a pdf file at The Daly book (ISBN 1-411-66597-X) is in src/

[sage-devel] Re: Sage 3.0 released

On Apr 23, 11:51 pm, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 4:43 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > >  We will be much more aggressive from now on in blacklisting know > > broken compilers since at least on OSX it should work out of the box > > because there

[sage-devel] Re: Sage 3.0 released

On Apr 23, 5:54 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > Could you type >./sage -br > form the SAGE_ROOT directory and send the output? Sure: -- sage: Building and installing modified SAGE library files. Installing c_lib g++

[sage-devel] Re: Test errors for Sage 3.0 on OS X

On Apr 23, 11:46 pm, Bjake Hammersholt Roune <[EMAIL PROTECTED]> wrote: > Sage builds without problems on this system Hi Bjarke, > SAGE Version 3.0, Release Date: 2008-04-22 > Mac OS X 10.5.2 > 1.8 GHz Intel Core 2 Duo > 2 GB RAM > gcc version 4.0.1 (Apple Inc. build 5465) > > while make test

[sage-devel] Re: Sage 3.0 released

On Wed, Apr 23, 2008 at 2:51 PM, mark mcclure <[EMAIL PROTECTED]> wrote: > > On Apr 23, 4:43 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > > We will be much more aggressive from now on in blacklisting know > > broken compilers since at least on OSX it should work out of the box >

[sage-devel] Re: Sage 3.0 released

On Apr 23, 4:43 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > We will be much more aggressive from now on in blacklisting know > broken compilers since at least on OSX it should work out of the box > because there is so little variety of the OS itself and Apple usually > is the tool chai

[sage-devel] Re: construction of finite fields GF(2^n)

2008/4/23 David Harvey <[EMAIL PROTECTED]>: > > > On Apr 23, 2008, at 5:38 PM, Martin Albrecht wrote: > > > 3) search for a tri- or pentanomial with some code similar to the > > one in blog > > post > > You might want to check the NTL code for whether NTL "auto-detects" > that you have suppl

[sage-devel] Re: rpy build script fails for sage-3.0

Michael, On Apr 23, 4:23 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > Hi Steve, > > we are now tracking the issue at #3011. > > On Apr 23, 10:08 pm, strogdon <[EMAIL PROTECTED]> wrote: > > --- CUT --- > > > > I've built sage previously, but without R installed. I suspect the > > instal

[sage-devel] Re: construction of finite fields GF(2^n)

Thanks for the debugging. I am trying it out (sage -br takes many minutes with this for some reason). If that works then I'll follow your suggestion to move this polynomial selection somewhere else. Should have a patch ready tomorrow... John 2008/4/23 Martin Albrecht <[EMAIL PROTECTED]>: > >

[sage-devel] Re: construction of finite fields GF(2^n)

On Apr 23, 2008, at 5:38 PM, Martin Albrecht wrote: > 3) search for a tri- or pentanomial with some code similar to the > one in blog > post You might want to check the NTL code for whether NTL "auto-detects" that you have supplied a sparse polynomial (and hence uses faster code for arith

[sage-devel] Test errors for Sage 3.0 on OS X

Sage builds without problems on this system SAGE Version 3.0, Release Date: 2008-04-22 Mac OS X 10.5.2 1.8 GHz Intel Core 2 Duo 2 GB RAM gcc version 4.0.1 (Apple Inc. build 5465) while make test produces the following errors (that I noticed) [listing begin] [...] sage -t devel/sage/sage/plot/a

[sage-devel] Re: Initial support for posets

As someone who is much more likely to use the non-poset lattices, I could certainly live with ZLattice (that's Z as in ZZ). Would either side get to keep plain Lattice? John 2008/4/23 Franco Saliola <[EMAIL PROTECTED]>: > > On Wed, Apr 23, 2008 at 4:05 PM, Robert Miller <[EMAIL PROTECTED]> wro

[sage-devel] Re: construction of finite fields GF(2^n)

On Wednesday 23 April 2008, John Cremona wrote: > Thanks, Martin. I agree with your comments. All I am really talking > about here is the time taken to construct the field -- I know that a > lot more work will be needed to get a really good finite field setup > in Sage (including arbitrary coerc

[sage-devel] Re: [fricas-devel] Re: [sage-devel] Re: FriCAS/Open-Axiom and SAGE

root wrote: > Gary, Hi Tim, > If you're interested in exploring Axiom's type system > the best source of material available is the Jenk's book. > It would be useful if Sage's type hierarchy was close to > the one Axiom uses, making it possible to share algorithms. > If you'll mail me a postal a

[sage-devel] Re: construction of finite fields GF(2^n)

Thanks, Martin. I agree with your comments. All I am really talking about here is the time taken to construct the field -- I know that a lot more work will be needed to get a really good finite field setup in Sage (including arbitrary coercions into extension fields, as previously discussed). I

[sage-devel] Re: notebook features discussion

> Does it go away if you pass the "fragile" option to the frame > environment? It seems that that is how people overcame this in the > past. Can you look in the source to the slides that was posted previously? > > \begin{frame}[fragile] Yes indeed, that works. I remember the problem, now that y

[sage-devel] Re: rpy build script fails for sage-3.0

Hi Steve, we are now tracking the issue at #3011. On Apr 23, 10:08 pm, strogdon <[EMAIL PROTECTED]> wrote: > Michael, > > Yes I do have R installed on my system. No, RHOMES is not set; > however, R_HOMES is set to /usr/lib64/R. Apparently, the R > installation does this. ok. We can certainly o

[sage-devel] Re: Trouble finding the normalizer of a subgroup

> Perhaps someone can help me figure this out. I am trying to create an > elementary abelian subgroup of a symmetric group and then look at its > normalizer. Here's what doesn't work: > > s6 = SymmetricGroup(6) > > c1 = s6([(1,2)]) > c2 = s6([(3,4)]) > c3 = s6([(5,6)]) > >

[sage-devel] Re: notebook features discussion

gerhard wrote: >> What problems are you having? Beamer and SageTeX are largely orthogonal, >> but there are some tricky bits with verbatim environments > > When I add a sageblock in a frame, e.g., > \begin{sageblock} > var('x') > f = log(sin(x)/x) > \end{sageblock} > > I get the error messa

[sage-devel] Re: Sage 3.0.rc1 released!

Andrzej Giniewicz wrote: > One test failed on standard rc1+clisp...p15, running 32 bit Arch linux > with GCC 4.3, /proc/cpuinfo below and doctest below it. > > cheers, > Andrzej. > > and only test that failed: > > sage -t devel/sage-main/sage/rings/complex_double.pyx > ***

[sage-devel] Re: Sage 3.0 released

On Apr 23, 10:04 pm, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 3:53 pm, mabshoff <[EMAIL PROTECTED] > > dortmund.de> wrote: > > This looks like Singular did not build properly. > > > > Please post a link to the  whole install.log here so I can take a > > look. Hi Mark, > Unfortunat

[sage-devel] Re: Initial support for posets

On Wed, Apr 23, 2008 at 4:05 PM, Robert Miller <[EMAIL PROTECTED]> wrote: > We might want to think about the naming conventions for Lattice. As > with all words in mathematics, this one has multiple meanings. A > lattice can be a poset with a meet and a join, or it can be a free > abelian gro

[sage-devel] Re: small documentation problem: "\ " at the end of a line

On Apr 23, 10:25 pm, John H Palmieri <[EMAIL PROTECTED]> wrote: > In the section of the tutorial on 3d plotting, > >   > > the continuation characters "\" all have spaces after them, which > messes up cutting and pasting.  Also in the section on Max

[sage-devel] Re: Sage 3.0 released

On Apr 23, 3:53 pm, mabshoff <[EMAIL PROTECTED] dortmund.de> wrote: > This looks like Singular did not build properly. > > Please post a link to the whole install.log here so I can take a > look. Unfortunately, I no longer have the whole install.log. In hopes of fixing the problem, I upgraded

[sage-devel] Re: Sage 3.0 released

On Apr 23, 3:54 pm, mhampton <[EMAIL PROTECTED]> wrote: > I'm not sure what the problem is, probably William Stein or Michael > Abshoff will be able to answer that, but maybe its simplest to just > upgrade your gcc with the latest stuff from apple. My gcc is build > 5465; I'm not sure how they

[sage-devel] small documentation problem: "\ " at the end of a line

In the section of the tutorial on 3d plotting, the continuation characters "\" all have spaces after them, which messes up cutting and pasting. Also in the section on Maxima, two of the backslash

[sage-devel] Re: Initial support for posets

On Wed, Apr 23, 2008 at 3:48 PM, mhampton <[EMAIL PROTECTED]> wrote: > I'm not really qualified to comment in detail, but I thought I would > mention that I am interested in computing face lattices of polytopes > as part of my polytope module. Perhaps you could comment on whether > there is

[sage-devel] Re: construction of finite fields GF(2^n)

On Wednesday 23 April 2008, John Cremona wrote: > There's a serious inefficiency in the construction of finite fields > GF(2^n) in Sage at the moment. > For n<=15 these are constructed of type > sage.rings.finite_field_givaro.FiniteField_givaro, about which I have > nothing to say now; for n>=16

[sage-devel] Re: [fricas-devel] Re: [sage-devel] Re: FriCAS/Open-Axiom and SAGE

Gary, Also of interest, the algebra hierarchy diagram and data hierarchy diagrams within Axiom (the endpapers from the Axiom book) are online at: Tim --~--~-~--~~~---~--~~ To post to this group, send

[sage-devel] Re: rpy build script fails for sage-3.0

Michael, Yes I do have R installed on my system. No, RHOMES is not set; however, R_HOMES is set to /usr/lib64/R. Apparently, the R installation does this. And yes I do have the install.log. The specific test fails as: sage -t devel/sage/sage/stats/test.py ***

[sage-devel] Re: rpy build script fails for sage-3.0

Michael, Yes I do have R installed on my system. No, RHOMES is not set; however, R_HOMES is set to /usr/lib64/R. Apparently, the R installation does this. And yes I do have the install.log. The specific test fails as: sage -t devel/sage/sage/stats/test.py ***

[sage-devel] Trouble finding the normalizer of a subgroup

Hi All, Perhaps someone can help me figure this out. I am trying to create an elementary abelian subgroup of a symmetric group and then look at its normalizer. Here's what doesn't work: s6 = SymmetricGroup(6) c1 = s6([(1,2)]) c2 = s6([(3,4)]) c3 = s6([(5,6)]) e8 = s6.subg

[sage-devel] Re: [fricas-devel] Re: [sage-devel] Re: FriCAS/Open-Axiom and SAGE

Gary, If you're interested in exploring Axiom's type system the best source of material available is the Jenk's book. It would be useful if Sage's type hierarchy was close to the one Axiom uses, making it possible to share algorithms. If you'll mail me a postal address (offline), I'll send you

[sage-devel] Re: Initial support for posets

We might want to think about the naming conventions for Lattice. As with all words in mathematics, this one has multiple meanings. A lattice can be a poset with a meet and a join, or it can be a free abelian group with an inner product. Normally I wouldn't bring such a thing up, but I'm working wi

[sage-devel] Re: Sage 3.0 released

Hi Mark! I'm not sure what the problem is, probably William Stein or Michael Abshoff will be able to answer that, but maybe its simplest to just upgrade your gcc with the latest stuff from apple. My gcc is build 5465; I'm not sure how they pick those version numbers. I know you are (or were?) a

[sage-devel] Re: Sage 3.0 released

On Apr 23, 9:23 pm, mark mcclure <[EMAIL PROTECTED]> wrote: > On Apr 23, 1:08 pm, Robert Bradshaw <[EMAIL PROTECTED]> > wrote: > > > >>  Are their binaries for OS X 10.4? > > > NO.  And there won't be until somebody volunteers to make them. > > > Can you make them? > > > Yes, do I just build and

[sage-devel] Re: Sage, Maxima, Lisp

On Apr 23, 1:08 pm, "Bill Page" <[EMAIL PROTECTED]> wrote: > Perhaps you have other ideas about how to achieve this kind of > interoperability? I could imagine for example linking Python directly > into the Aldor C run-time system or maybe linking the Python into the > lisp image that runs Axiom?

[sage-devel] Re: rpy build script fails for sage-3.0

On Apr 23, 4:52 pm, strogdon <[EMAIL PROTECTED]> wrote: Hi, > On my Gentoo box I unpacked the subject tarball, changed to the sage > directory and did a make with the results: > > gcc version 4.1.2 (Gentoo 4.1.2 p1.0.2) > > *

[sage-devel] construction of finite fields GF(2^n)

There's a serious inefficiency in the construction of finite fields GF(2^n) in Sage at the moment. For n<=15 these are constructed of type sage.rings.finite_field_givaro.FiniteField_givaro, about which I have nothing to say now; for n>=16 they have type sage.rings.finite_field_ntl_gf2e.FiniteFiel

[sage-devel] Re: Initial support for posets

I'm not really qualified to comment in detail, but I thought I would mention that I am interested in computing face lattices of polytopes as part of my polytope module. Perhaps you could comment on whether there is (or could be) anything in your code that might help me out with that. I think its

[sage-devel] Re: [fricas-devel] Re: [sage-devel] Re: FriCAS/Open-Axiom and SAGE

"Gary Furnish" <[EMAIL PROTECTED]> writes: > I'd be interested in hearing which features of FriCAS/OpenAxiom has that > might be useful in more detail. I'm not quite sure what you are interested in. I attach some things that I know to be working well or that I used recently below. > My main

[sage-devel] Re: Sage 3.0 released

On Apr 23, 1:08 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > >> Are their binaries for OS X 10.4? > > NO. And there won't be until somebody volunteers to make them. > > Can you make them? > > Yes, do I just build and do sage -bdist? I attempted to compile sage 3.0 on my Mac G5 running OS

[sage-devel] Re: [fricas-devel] Re: Sage, Maxima, Lisp

2008/4/23 Waldek Hebisch wrote: > ... > For FriCAS in longer run dropping Lisp is likely -- most Lisp code > is machine generated during FriCAS build. With enough effort we > could directly generate C code. Currently effort to drop Lisp would > be prohibitive, but the FriCAS code is constanl

[sage-devel] Re: [fricas-devel] Re: [sage-devel] Re: FriCAS/Open-Axiom and SAGE

On Wed, Apr 23, 2008 at 1:48 PM, Gary Furnish wrote: > ... > Right now, most functionality of the sage.calculus module is dictated > strictly by how maxima is designed. As we move to our own internal > representation, this obviously will not be sufficient. It is not immediately obvious to me tha

[sage-devel] Initial support for posets

Dear all, I've posted on trac the current version of my posets code. There is still much to be done, some algorithms need to be improved and others need to be implemented. (There are no NotImplementedErrors.) http://trac.sagemath.org/sage_trac/ticket/2519 But before I continue working, I'd li

[sage-devel] Re: [fricas-devel] Re: [sage-devel] Re: FriCAS/Open-Axiom and SAGE

No doubt the sage system is a bit too ad hoc. However, this is something that will be fixed in the symbolics rewrite. While externally it will maintain most backwards compatibility, internally it will be vastly different (for example, elements (including variables) in the "symbolic ring" (which i

[sage-devel] Re: Sage 3.0 released

I have a MAC OX X 10.4.4 build in process. Its on a PowerPC (G4) I'll make it available when it completes. Tim --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] Fo

[sage-devel] Re: Sage 3.0 released

On Apr 23, 2008, at 10:06 AM, William Stein wrote: > > On Wed, Apr 23, 2008 at 10:03 AM, Robert Bradshaw > <[EMAIL PROTECTED]> wrote: >> >> Are their binaries for OS X 10.4? > > NO. And there won't be until somebody volunteers to make them. See > my long email about this a few minutes ago in Sa

[sage-devel] Re: Sage 3.0 released

On Wed, Apr 23, 2008 at 10:03 AM, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > > Are their binaries for OS X 10.4? NO. And there won't be until somebody volunteers to make them. See my long email about this a few minutes ago in Sage-support. Can you make them? > > On Apr 23, 2008, at 4:58 A

[sage-devel] Re: Sage 3.0 released

Are their binaries for OS X 10.4? On Apr 23, 2008, at 4:58 AM, mabshoff wrote: > > [Note: If you are interested in announcements only please subscribe to > sage-announce. It is limited to roughly one email every ten days.] > > Hello folks, > > Sage 3.0 has been released on April 21st, 2008. It is

[sage-devel] Re: notebook features discussion

> What problems are you having? Beamer and SageTeX are largely orthogonal, > but there are some tricky bits with verbatim environments When I add a sageblock in a frame, e.g., \begin{sageblock} var('x') f = log(sin(x)/x) \end{sageblock} I get the error message Runaway argument? ! Paragraph

[sage-devel] Re: Sage build failure

On Wed, Apr 23, 2008 at 9:46 AM, <[EMAIL PROTECTED]> wrote: > > The install.log file is at > > This fails with "internal compiler error": '__pyx_pf_4sage_7modules_18real_double_vector_28RealDoubleVectorSpaceElement___init_

[sage-devel] Sage build failure

The install.log file is at This fails on fedora 5 [EMAIL PROTECTED] sage-3.0]# uname -a Linux localhost.localdomain 2.6.18-1.2239.fc5 #1 Fri Nov 10 13:04:06 EST 2006 i686 i686 i386 GNU/Linux You have new mail in /var/spool/mail/root [EMAIL PROTECT

[sage-devel] Re: FriCAS/Open-Axiom and SAGE

On Wed, Apr 23, 2008 at 4:28 AM, Michael.Abshoff wrote: > > Martin Rubey wrote: > > > I do not see how the problem of differing representations can be > > resolved. Up to now I thought that Sage simply doesn't have an > > "internal" representation, and just uses the one from the external > >

[sage-devel] rpy build script fails for sage-3.0

On my Gentoo box I unpacked the subject tarball, changed to the sage directory and did a make with the results: gcc version 4.1.2 (Gentoo 4.1.2 p1.0.2) RHOMES= [] DEBUG= True Setting RHOMES t

[sage-devel] Sage 3.0.1 Merge Cycle Opened - Game Plane

Hello folks, since 3.0 is out the inevitable happens: 3.0.1 is next release. We would like to do a mostly bug fix release, but that somehow depends on how buggy 3.0 is. So far the issues with the notebook seems to be only big issues reported so far. I did talk to Robert in IRC earlier today and

[sage-devel] Sage 3.0 released

[Note: If you are interested in announcements only please subscribe to sage-announce. It is limited to roughly one email every ten days.] Hello folks, Sage 3.0 has been released on April 21st, 2008. It is available at http://sagemath.org/download.html * About Sage (http://www.sagema

[sage-devel] Re: FriCAS/Open-Axiom and SAGE

[this email will likely bounce somewhere, so if it doesn't show up in some place please forward] Martin Rubey wrote: > Dear Michael, Hi Martin, > just a short recap, whether I have understood things correctly: > >the problem you currently face with external symbolic calculus is that the >

[sage-devel] FriCAS/Open-Axiom and SAGE

Dear Michael, just a short recap, whether I have understood things correctly: the problem you currently face with external symbolic calculus is that the representation of the objects is not identical in SAGE and in the external progam (Maxima). you are using something called "pexpec