[sage-devel] Reviewer needed to review 9 lines of autoconf script.

2011-03-29 Thread David Kirkby
http://trac.sagemath.org/sage_trac/ticket/9978 needs review, but it needs someone with experience of writing autoconf scripts to review it. The actual extra "code" added is just 9 lines, though there's a few lines of comments too http://trac.sagemath.org/sage_trac/attachment/ticket/9978/9978-Chan

Re: [sage-devel] Reviewer needed to review 9 lines of autoconf script.

2011-03-29 Thread Nicolas M. Thiery
Hi David, On Tue, Mar 29, 2011 at 09:10:04AM +0100, David Kirkby wrote: > http://trac.sagemath.org/sage_trac/ticket/9978 > > needs review, but it needs someone with experience of writing autoconf > scripts to review it. The actual extra "code" added is just 9 lines, > though there's a few

[sage-devel] Re: Patch submitting procedures

2011-03-29 Thread slabbe
> 1) When submitting a patch, make sure there is reasonable *commit > message* (use hg qrefresh -e to set the message). or hg qrefresh -m "#: Commit message" to do it from the command line. I think if one does hg qrefresh -e "#: Commit message" it erases the patch and replaces it by t

Re: [sage-devel] Reviewer needed to review 9 lines of autoconf script.

2011-03-29 Thread Dr. David Kirkby
On 03/29/11 09:34 AM, Nicolas M. Thiery wrote: Hi David, Hi Nicolas I did not actually run the code, especially on AIX, but trust you did (both with and without libm installed). Reading it sounds very reasonable; I am thus ready to give it a positive review. Yes, I did test it. I'v

[sage-devel] Re: Patch submitting procedures

2011-03-29 Thread Jason Grout
On 3/28/11 4:36 AM, Jeroen Demeyer wrote: Also the correct(!) ticket number should appear on the first line of the commit message. Does the patch merging script not automatically do this? I thought at one time somebody added this. Again, the patch merging script already knows this, and if t

[sage-devel] Re: http://flask.sagenb.org -- test it!!!

2011-03-29 Thread Jason Grout
On 3/27/11 10:28 AM, Mike Hansen wrote: This still doesn't fix the issue for me, since the Jmol applet then requests the .zip file from the worksheet directory rather than the cell directory (and gets a 404). However, this should not be too hard to track down. I've posted a fix to #11078 (thou

[sage-devel] Re: http://flask.sagenb.org -- test it!!!

2011-03-29 Thread Jason Grout
On 3/27/11 10:28 AM, Mike Hansen wrote: The issue is that the secure cookie that Flask uses is sent as httponly, which the Java applet won't send. Adding this patch to the notebook code will fix that: Rado: I have applied the patch to my clone at https://code.google.com/r/jasongrout-sagenb/.

Re: [sage-devel] Re: Patch submitting procedures

2011-03-29 Thread Jeroen Demeyer
On 2011-03-29 13:15, Jason Grout wrote: > On 3/28/11 4:36 AM, Jeroen Demeyer wrote: >> Also the correct(!) ticket >> number should appear on the first line of the commit message. > > Does the patch merging script not automatically do this? This is not the case. It would be possible to do this au

[sage-devel] Re: Patch submitting procedures

2011-03-29 Thread Jason Grout
On 3/29/11 6:58 AM, Jeroen Demeyer wrote: On 2011-03-29 13:15, Jason Grout wrote: On 3/28/11 4:36 AM, Jeroen Demeyer wrote: Also the correct(!) ticket number should appear on the first line of the commit message. Does the patch merging script not automatically do this? This is not the case.

[sage-devel] Re: http://flask.sagenb.org -- test it!!!

2011-03-29 Thread Jason Grout
On 3/25/11 9:03 PM, William Stein wrote: Hi, Please find bugs in http://flask.sagenb.org. Is it slow? Fast? Broken in *any* way at all? This is the result of a huge amount of awesome work of Rado Kirov and Mike Hansen and many, many others. There is exactly one known bug -- JMOL 3d graphics

[sage-devel] Valgrind package very old

2011-03-29 Thread Dr. David Kirkby
The optional package 'valgrind' for Sage is version 3.3.1, which was released in June 2008. It does not support OS X. The latest release of valgrind http://valgrind.org/info/platforms.html supports OS X too. It would probably be useful if someone familiar with the package updated this option

[sage-devel] Re: Valgrind package very old

2011-03-29 Thread Volker Braun
I also noticed that the valgrind package is old; In particular it doesn't even compile on Fedora 14. But then its such a commonly-used tool that its already on every machine that is used for software development. The fact that nobody every complained about the outdated valgrind spkg should prob

Re: [sage-devel] Re: Valgrind package very old

2011-03-29 Thread Dr. David Kirkby
On 03/29/11 04:36 PM, Volker Braun wrote: I also noticed that the valgrind package is old; In particular it doesn't even compile on Fedora 14. But then its such a commonly-used tool that its already on every machine that is used for software development. The fact that nobody every complained abou

[sage-devel] Re: Valgrind package very old

2011-03-29 Thread Jaap Spies
Dr. David Kirkby wrote: On 03/29/11 04:36 PM, Volker Braun wrote: I also noticed that the valgrind package is old; In particular it doesn't even compile on Fedora 14. But then its such a commonly-used tool that its already on every machine that is used for software development. The fact that nob

Re: [sage-devel] Re: Valgrind package very old

2011-03-29 Thread Justin C. Walker
On Mar 29, 2011, at 10:09 , Dr. David Kirkby wrote: > On 03/29/11 04:36 PM, Volker Braun wrote: >> I also noticed that the valgrind package is old; In particular it doesn't >> even compile on Fedora 14. But then its such a commonly-used tool that its >> already on every machine that is used for s

[sage-devel] Re: [sage-edu] Re: Teaching Sage at AIMS

2011-03-29 Thread Jan Groenewald
Hi The deadline has been extended. The website will be updated shortly. We are still looking for a SAGE (problem solving type course, experimental mathematics using SAGE) course around September/October 2011. Feel free to mail me off list for queries. Regards, Jan On Thu, Jan 20, 2011 at 02:14

Re: [sage-devel] Re: Valgrind package very old

2011-03-29 Thread Dr. David Kirkby
On 03/29/11 07:12 PM, Jaap Spies wrote: Dr. David Kirkby wrote: On 03/29/11 04:36 PM, Volker Braun wrote: I also noticed that the valgrind package is old; In particular it doesn't even compile on Fedora 14. But then its such a commonly-used tool that its already on every machine that is used fo

[sage-devel] How to cope with a long method resolution order?

2011-03-29 Thread Simon King
Hi! Tickets #9944 and #9138 provide some nice features, but slow things down. It seems to me that the reason of the performance loss is that the patches from these tickets make the method resolution order of polynomial rings much longer - in some cases the length doubles (15 versus 39 steps until

Re: [sage-devel] How to cope with a long method resolution order?

2011-03-29 Thread Florent Hivert
Hi Simon, On Tue, Mar 29, 2011 at 12:07:15PM -0700, Simon King wrote: > Hi! > > Tickets #9944 and #9138 provide some nice features, but slow things > down. It seems to me that the reason of the performance loss is that > the patches from these tickets make the method resolution order of > p

Re: [sage-devel] Re: Patch submitting procedures

2011-03-29 Thread David Roe
If the script automatically prepended: > > Trac #: > > to the start of every commit message, then: > > 1. the ticket number text would be uniform > > 2. if a wrong ticket number was indicated, it would be obvious which was > the correct ticket number, as it's always first in the standard forma

[sage-devel] Problems building Sage with gcc 4.6.0

2011-03-29 Thread Dr. David Kirkby
I thought I'd try Sage with gcc 4.6.0, which was released a few days ago. After installing gcc on my Sun Ultra 27 and trying to compile sage-4..7.alpha2, I get 3 failures. I run "make -k" to skip over errors. I'm hoping these are the only three. I suspect the PolyBoRi issue will only effect So

[sage-devel] Re: http://flask.sagenb.org -- test it!!!

2011-03-29 Thread Jason Grout
On 3/25/11 9:03 PM, William Stein wrote: Hi, Please find bugs in http://flask.sagenb.org. Is it slow? Fast? Broken in *any* way at all? For some reason, I can't insert text cells. I insert a text cell and the page refreshes. My guess is that somehow the state numbers get out of sync and

[sage-devel] Re: http://flask.sagenb.org -- test it!!!

2011-03-29 Thread Benjamin Jones
On Mar 28, 10:45 pm, mhampton wrote: > Hey Harald (et al)- > > I am wondering if this is a general bug in the sage notebook - I seem > to be having this problem with sage-4.7.alpha2 (not running the flask > notebook, just the usual one).  Can someone else try this to confirm? > > -Marshall > > O

[sage-devel] Re: http://flask.sagenb.org -- test it!!!

2011-03-29 Thread Jason Grout
On 3/29/11 7:07 PM, Jason Grout wrote: On 3/25/11 9:03 PM, William Stein wrote: Hi, Please find bugs in http://flask.sagenb.org. Is it slow? Fast? Broken in *any* way at all? For some reason, I can't insert text cells. I insert a text cell and the page refreshes. My guess is that somehow the

[sage-devel] Online Sage MAA PREP workshop

2011-03-29 Thread Jason Grout
Hi everyone, Just FYI, for your best friends: Karl-Dieter Crisman and I are running an online Sage PREP workshop through the MAA (in the U.S.). If you know people that want to start using Sage in undergraduate teaching, but need someone to help them through the process, the PREP workshop is a

[sage-devel] Re: http://flask.sagenb.org -- test it!!!

2011-03-29 Thread Rado
Great job Jason and Mike. Seems the Jmol problem is fixed. At least it works here on ubuntu and firefox 3.6 and chromium 10 with sun's java. I pulled Jason's changes into my repo, so every one who pulled from me can do just hg pull; hg up. Finally, there needs to be one line change done in the sag

Re: [sage-devel] Re: Valgrind package very old

2011-03-29 Thread Robert Miller
>> I also noticed that the valgrind package is old; In particular it doesn't >> even compile on Fedora 14. But then its such a commonly-used tool that its >> already on every machine that is used for software development. The fact >> that nobody every complained about the outdated valgrind spkg sho

[sage-devel] sage notebook with many Jmol viewers

2011-03-29 Thread jtyard
I am having issues with sage notebooks that contain more than five instances of the Jmol viewer. In short, if I create a notebook with more than 5 Jmol viewers, save, then reload it, I get an unresponsive script error in Firefox, Safari and Chrome. I've done some peeking around on the trac serve

[sage-devel] Re: How to cope with a long method resolution order?

2011-03-29 Thread Simon King
Hi Florent, On 29 Mrz., 21:54, Florent Hivert wrote: > So it seems that there is no difference... Well actually I just figured out > that this has something to do with Cython: if I change > > class End(object): > > to > > class End(SageObject): > > Then: > > sage: timeit('obj_long.toto()',number=

Re: [sage-devel] Re: How to cope with a long method resolution order?

2011-03-29 Thread David Roe
I think that base_ring and parent are cpdef'd methods (I don't want to look it up at the moment). You want to be a little careful overriding such methods with Python functions living in the dictionary, because then the functions called by Cython code that knows the type of your object, and the cod

[sage-devel] Re: How to cope with a long method resolution order?

2011-03-29 Thread Simon King
Hi David, On 30 Mrz., 08:00, David Roe wrote: > I think that base_ring and parent are cpdef'd methods (I don't want to look > it up at the moment).  You want to be a little careful overriding such > methods with Python functions living in the dictionary, because then the > functions called by Cyt

[sage-devel] Re: How to cope with a long method resolution order?

2011-03-29 Thread Simon King
On 30 Mrz., 08:20, Simon King wrote: > "base" is a Python method (I looked it up), I meant to say: "a def method, not cpdef", but of course it is in a .pyx file. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+u

Re: [sage-devel] How to cope with a long method resolution order?

2011-03-29 Thread Nicolas M. Thiery
On Tue, Mar 29, 2011 at 12:07:15PM -0700, Simon King wrote: > Tickets #9944 and #9138 provide some nice features, but slow things > down. It seems to me that the reason of the performance loss is that > the patches from these tickets make the method resolution order of > polynomial rings much longe

Re: [sage-devel] Re: How to cope with a long method resolution order?

2011-03-29 Thread Nicolas M. Thiery
On Wed, Mar 30, 2011 at 02:00:22AM -0400, David Roe wrote: >I think that base_ring and parent are cpdef'd methods (I don't want to >look it up at the moment). Not at this point apparently: category_object.pyx, line 479: def base_ring(self): # This should be in a category or elsewhere,

[sage-devel] 4.6.2 build on Ubuntu 11.04 alpha 3 fails on crypt.so

2011-03-29 Thread Jan Groenewald
Hi Ubuntu 11.04 is still alpha 3, but in the meantime I've had to install it for graphics/wireless/sound driver reasons. jan@mamadou-laptop:/usr/local/src/sage-4.6.2$ lsb_release -d Description:Ubuntu Natty (development branch) jan@mamadou-laptop:/usr/local/src/sage-4.6.2$ uname -a Linux mama