[sage-devel] Re: sage-4.0.2

2009-06-20 Thread kcrisman
Compiled fine on OSX.4 G4 PPC. There were a lot of warnings in Sphinx at the very end about duplicate references within the English tutorial, usually with bibliography.rst. - kcrisman --~--~-~--~~~---~--~~ To post to this group, send email to

[sage-devel] Re: sage-4.0.2

2009-06-20 Thread Andrzej Giniewicz
for gcc 4.4) - there is patch against singular spkg from 4.0.2 - http://giniu.ravenlord.ws/singular-3-1-0-2-20090620.diff - and spkg itself - http://giniu.ravenlord.ws/singular-3-1-0-2-20090620.spkg - wasn't doing any patches for Sage for a while so would be good to check if before commit, I

[sage-devel] building sage in parallel in parallel

2009-06-20 Thread William Stein
Hi, I just tried the following. 1. Take a clean Sage-4.0.2 tarball and edit SAGE_ROOT/spkg/install replacing the line time make -f standard/deps $1 by time make -j20 -f standard/deps $1 2. make. This builds a whole bunch of different spkg's in parallel. At one point spkg/install gets

[sage-devel] Re: Sage 4.0.1.alpha0 linbox trying to build before blas was installed

2009-06-20 Thread William Stein
On Fri, Jun 19, 2009 at 9:21 PM, Dr. David Kirkbydavid.kir...@onetel.net wrote: Dr. David Kirkby wrote: In the process of building Sage on t2, I noticed another failure, which I'm somewhat surprised has not been seen on all platforms. I've submitted this as ticket 6278, where more

[sage-devel] Re: Sage 4.0.1.alpha0 linbox trying to build before blas was installed

2009-06-20 Thread Dr. David Kirkby
William Stein wrote: On Fri, Jun 19, 2009 at 9:21 PM, Dr. David How can the bug be closed. I've closed it. Only a few people have the option to close tickets right now. William Thank you. That's one less Solaris bug to worry over. Plenty more though to occupy our time. dave

[sage-devel] mpfr 2.4.1 build issue on Solaris with gcc 4.4.0

2009-06-20 Thread Dr. David Kirkby
Before building gcc 4.4.0 on 't2' I needed to build mpfr, as it is perquisite for gcc. I built the latest version of mpfr (2.4.1) using the Sun supplied gcc 3.4.2 in /usr/sfw/bin. mpfr built and passed all 148 tests. With the aid: 1) The aid of a patch to atlas

[sage-devel] Display Sage version on notebook login page?

2009-06-20 Thread Pat LeSmithe
Are there objections to displaying something like Sign into the Sage Notebook v4.0.2 in place of Sign into the Sage Notebook on the notebook log-in page? It often helps to know which version is running on sagenb.org or alpha.sagenb.org, before logging in. The actual change would be to use,

[sage-devel] Re: Display Sage version on notebook login page?

2009-06-20 Thread William Stein
On Sat, Jun 20, 2009 at 2:09 PM, Pat LeSmitheqed...@gmail.com wrote: Are there objections to displaying something like Sign into the Sage Notebook v4.0.2 in place of Sign into the Sage Notebook on the notebook log-in page?  It often helps to know which version is running on sagenb.org

[sage-devel] Re: Display Sage version on notebook login page?

2009-06-20 Thread Pat LeSmithe
William Stein wrote: On Sat, Jun 20, 2009 at 2:09 PM, Pat LeSmitheqed...@gmail.com wrote: Are there objections to displaying something like Sign into the Sage Notebook v4.0.2 in place of Sign into the Sage Notebook on the notebook log-in page? It often helps to know which version is

[sage-devel] Integration in new Sage symbolics

2009-06-20 Thread Golam Mortuza Hossain
Hi, I am wondering whether there is any policy/framework for hooking-up a specialized integration code as a part of integration algorithm in new symbolic? I have been writing code for integration involving Dirac delta generalized function to include the same in Sage. The form of integrand that

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-20 Thread John Cremona
2009/6/20 Craig Citro craigci...@gmail.com: That did the trick -- ran fine and no failure line at the end.  (I moved that line to the end as suggested) Interesting ... that means that the call to sys.exit(0) is generating an exception that's getting caught in the except: clause. Can you

[sage-devel] Re: sage-4.0.2

2009-06-20 Thread Andrzej Giniewicz
). Anyway - had to patch libsingular (it use deprecated strchr form in 2 places, simple cast is enough to fix it just as recommended on official porting guide for gcc 4.4) - there is patch against singular spkg from 4.0.2 - http://giniu.ravenlord.ws/singular-3-1-0-2-20090620.diff - and spkg itself

[sage-devel] Nasty simplify() bug in symbolics

2009-06-20 Thread Golam Mortuza Hossain
Hi, It seems that there is a major bug in new symbolics simplify() method involving D and symbolic function (Sage-4.0.1). --- sage: f(x) = function('f',x) sage: f(-x).diff(x) -D[0](f)(-x) sage: f(-x).diff(x).simplify() -D[0](f)(x) --- Notice that simplify() causes f(-x) to

[sage-devel] Fwd: sigsam.org/awards/jenks/

2009-06-20 Thread Harald Schilly
A nomination for this prize (and similar ones) would be a huge boost for sage. I hope we don't forget to ask for you support! ;) Harald -- Forwarded message -- From: Frank Sottile sott...@math.tamu.edu Date: Sat, Jun 20, 2009 at 18:49 PS: (share the following with your team:    

[sage-devel] Re: sage 4.0.2.rc3 released

2009-06-20 Thread Craig Citro
Interesting ... that means that the call to sys.exit(0) is generating an exception that's getting caught in the except: clause. Can you file a ticket for this? I'll happily review it. :) I created a ticket #6364, without a patch though since it's outside SAGE_ROOT/devel. Actually, there's

[sage-devel] Re: Sage 4.0.3 (or 4.1?)

2009-06-20 Thread Nicolas M. Thiery
On Fri, Jun 19, 2009 at 12:00:19PM -0700, Tom Boothby wrote: I'm the release manager for sage-4.0.3. Python to 2.6, and if I succeed, I'll rename the release to sage-4.1. In about an hour, I'm going to send out review requests. Tom: thanks very much for your time on this! To all (potential)

[sage-devel] Re: tinymce

2009-06-20 Thread Pat LeSmithe
William Stein wrote: What about control-enter? Can you make it so control-enter = linebreak shift-enter = submit ? Control-enter is bound to spliteval_cell. To make control-shift-enter, say, insert a line break, try augmenting notebook.py's tinyMCE.init()'s setup with some code