[sage-devel] Final stretch for 3.1.2 reviews
Hello folks, the end of the 3.1.2 release cycle is near - at least the point where we will only merge bug fixes or even critical bug fixes. So if you have things sitting in trac waiting to make it in please find somebody to review the patch. Please also make sure that the positively reviewed patch shows up at report 11 since that is what I use to find them. One issue I found today is that that report does not pick up ticket if there is more than one space between positive and reviewed. Report 12 in trac are tickets that need work and many of them have been sitting there for a while. So if one of those belongs to you please have a look. Cheers, Michael --~--~-~--~~~---~--~~ 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/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Final stretch for 3.1.2 reviews
I hope I didn't kill #1115's chances by relabelling it from a bug fix to an enhancement, since I didn't just fix the bug... The only problem with the current patch is that we found a call to dumps() crashes on a 64-bit machine but is fine on a 32-bit machine. Anyone have any idea what might cause that? John 2008/9/2 mabshoff [EMAIL PROTECTED]: Hello folks, the end of the 3.1.2 release cycle is near - at least the point where we will only merge bug fixes or even critical bug fixes. So if you have things sitting in trac waiting to make it in please find somebody to review the patch. Please also make sure that the positively reviewed patch shows up at report 11 since that is what I use to find them. One issue I found today is that that report does not pick up ticket if there is more than one space between positive and reviewed. Report 12 in trac are tickets that need work and many of them have been sitting there for a while. So if one of those belongs to you please have a look. Cheers, Michael --~--~-~--~~~---~--~~ 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/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Copying/moving worksheets
We are running a VMWare server for fall classes. However, we have run into the disturbing problem that if we want to use a newer version of Sage (such as to get the plotting improvements), we would need to (quoting William in the earlier version of this thread) upload them tediously one by one. This basically means we can't upgrade Sage in the middle of the semester if even a few students decide to use Sage, and we are hoping for a score or two or them to do so. Also, will the user info migrate, or would they have to be readded? One thing the admin has tried is copying old worksheets into different possible directories, just as a crazy thing to do, for instance given http://groups.google.com/group/sage-support/browse_thread/thread/ef2d39efd31f5e28/336519680f4e10ae?lnk=gstq=moving+worksheets#336519680f4e10ae . Now, http://www.sagemath.org/doc/tut/node45.html makes it clear where the worksheet pages are supposed to live. But today I verified that the version of at least one of my worksheets that in fact shows up in the browser lives in ~/sage_notebook/worksheets/admin , while others definitely live in ~/.sage/sage_notebook/worksheets/admin . It isn't a case of a reference, either, because there is an older version of the first worksheet in the .sage directory, while in the other case the worksheet *only* exists in the .sage/ directory. So now I am unsure whether I should even try to move my own worksheets around on my personal computer! I would love to try to fix this but unfortunately know nothing about these issues, and our admin is not likely to try to fix the code. Is there any sense (on support or devel) of whether either of these things might be resolved soon (or in the second case, if it's even been noticed before - I haven't seen it in a fairly exhaustive sage- support search)? We would obviously prefer if yes, but even if not, then at least we can prepare for this properly and not send students on wild goose chases for their data. Thanks much. - kcrisman --~--~-~--~~~---~--~~ 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/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.1.2.alpha4 released
Build reports 32-bit: just the already known failures: sage -t devel/sage/sage/stats/hmm/chmm.pyx sage -t devel/sage/sage/stats/hmm/hmm.pyx sage -t devel/sage/sage/interfaces/gp.py on Linux version 2.6.24-19-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Aug 20 22:56:21 UTC 2008 64-bit: just one failure: sage -t devel/sage/sage/interfaces/lisp.py on Linux version 2.6.18.8-0.3-default ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Tue Apr 17 08:42:35 UTC 2007 which I think is also in Michael's list of known issues. John 2008/9/2 Timothy Clemans [EMAIL PROTECTED]: There is a Notebook blocker at http://trac.sagemath.org/sage_trac/ticket/3960 A critical one at http://trac.sagemath.org/sage_trac/ticket/3918 Two major ones that are pretty serious to me: http://trac.sagemath.org/sage_trac/ticket/3957 and http://trac.sagemath.org/sage_trac/ticket/3711 On Tue, Sep 2, 2008 at 9:06 AM, mabshoff [EMAIL PROTECTED] wrote: Hello folks, this is alpha4 and more progress toward the final 3.1.2. As some people have noticed this release is getting larger than the original 3.1, but I guess such is life. THe m4ri issues have been sorted out, but there are still four major issues: * ghmm/hmm * gp.py doctest failing on 32 but machine * lisp/sage0 doctest failures due to issues with newlines/ipython escape character issues/synchronization * PolyBori 0.5 and ATLAS 3.8.2 still not updated. So expect rc0 with hopefully most of the above fixed. It has been a little over 2 weeks since 3.1.1, so we need to get this release out of the door. Sources and a sage.math only binary is in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.2/ Cheers, Michael Merged in Sage 3.1.alpha4: #309: Alex Ghitza: rationals enumeration not monotone in height [Reviewed by John Cremona] #1834: Alex Ghitza: General linear group over ZZ hangs in __call__ [Reviewed by John Cremona] #2547: Jason Merrill: Implement gradient(), hessian() for callable symbolic expressions [Reviewed by Mike Hansen] #3451: Alex Ghitza: inaccurate error message in scheme morphisms [Reviewed by John Cremona] #3622: Robert Bradshaw: numerical fast integration using fast float [Reviewed by Jason Merrill] #3805: Jason Merrill: sage gets basic arithmetic with sqrt(3) wrong [Reviewed by Michael Abshoff] #3921: Jason Merrill: calculus -- solve(..., constant) should complain by default [Reviewed by Alex Ghitza] #3969: Robert Brashaw: Matrix_mod2_dense hashs follow-up (see #3724)) [Reviewed by Martin Albrecht] #3974: Chris Wuthrich: renaming of integral_weierstrass_model to integral_short_weierstrass_model [Reviewed by John Cremona] #4016: Alex Ghitza: improve doctests to schemes/generic/scheme.py [Reviewed by Robert Bradshaw] #4017: Michael Abshoff: Sage 3.1.2.alpha1 - PPC OSX: numerical noise in sage/stats/hmm/chmm.pyx [Reviewed by Mike Hansen] #4018: Robert Bradshaw: casting of non t_INT pari integers [Reviewed by Alex Ghitza] #4019: Robert Bradshaw: numerator and denominator for QQ[x] [Reviewed by Alex Ghitza] #4020: Robert Bradshaw: fraction field doctests [Reviewed by Mike Hansen] #4024: Martin Albrecht: upgrade M4RI to newest upstream release (20080901) [Reviewed by Michael Abshoff] #4025: Michael Abshoff, Mike Hansen: Sage 3.1.2.alpha3: benchmark.py runs Maple tests that should be optional [Reviewed by David Joyner] #4027: Martin Albrecht: Sage 3.1.2.alpha3: matrix_mod2_dense.pyx doctest failure on 32 bits [Reviewed by Michael Abshoff] #4028: Mike Hansen: doctest and improve sage/interfaces/axiom.py [Reviewed by Michael Abshoff] #4030: Jason Merrill: Vectors of callable things should be callable [Reviewed by Mike Hansen] #4031: Jason Merrill: Callable symbolic expressions should allow keyword args [Reviewed by Mike Hansen] #4032: Michael Abshoff: Add x86 Solaris build support for libSingular [Reviewed by Martin Albrecht] #4033: Michael Abshoff: disabled libiconv on Solaris for the r.spkg [Reviewed by Martin Albrecht] #4034: Michael Abshoff: Fix rubiks.spkg build on Solaris [Reviewed by Martin Albrecht] #4037: Alex Ghitza: list_of_first_n() broken in interact.py [Reviewed by John Cremona] --~--~-~--~~~---~--~~ 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/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.1.2.alpha4 released
installed fine and all tests passed on amd64 hardy heron. On Tue, Sep 2, 2008 at 9:06 AM, mabshoff [EMAIL PROTECTED] wrote: Hello folks, this is alpha4 and more progress toward the final 3.1.2. As some people have noticed this release is getting larger than the original 3.1, but I guess such is life. THe m4ri issues have been sorted out, but there are still four major issues: * ghmm/hmm * gp.py doctest failing on 32 but machine * lisp/sage0 doctest failures due to issues with newlines/ipython escape character issues/synchronization * PolyBori 0.5 and ATLAS 3.8.2 still not updated. So expect rc0 with hopefully most of the above fixed. It has been a little over 2 weeks since 3.1.1, so we need to get this release out of the door. Sources and a sage.math only binary is in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.2/ Cheers, Michael Merged in Sage 3.1.alpha4: #309: Alex Ghitza: rationals enumeration not monotone in height [Reviewed by John Cremona] #1834: Alex Ghitza: General linear group over ZZ hangs in __call__ [Reviewed by John Cremona] #2547: Jason Merrill: Implement gradient(), hessian() for callable symbolic expressions [Reviewed by Mike Hansen] #3451: Alex Ghitza: inaccurate error message in scheme morphisms [Reviewed by John Cremona] #3622: Robert Bradshaw: numerical fast integration using fast float [Reviewed by Jason Merrill] #3805: Jason Merrill: sage gets basic arithmetic with sqrt(3) wrong [Reviewed by Michael Abshoff] #3921: Jason Merrill: calculus -- solve(..., constant) should complain by default [Reviewed by Alex Ghitza] #3969: Robert Brashaw: Matrix_mod2_dense hashs follow-up (see #3724)) [Reviewed by Martin Albrecht] #3974: Chris Wuthrich: renaming of integral_weierstrass_model to integral_short_weierstrass_model [Reviewed by John Cremona] #4016: Alex Ghitza: improve doctests to schemes/generic/scheme.py [Reviewed by Robert Bradshaw] #4017: Michael Abshoff: Sage 3.1.2.alpha1 - PPC OSX: numerical noise in sage/stats/hmm/chmm.pyx [Reviewed by Mike Hansen] #4018: Robert Bradshaw: casting of non t_INT pari integers [Reviewed by Alex Ghitza] #4019: Robert Bradshaw: numerator and denominator for QQ[x] [Reviewed by Alex Ghitza] #4020: Robert Bradshaw: fraction field doctests [Reviewed by Mike Hansen] #4024: Martin Albrecht: upgrade M4RI to newest upstream release (20080901) [Reviewed by Michael Abshoff] #4025: Michael Abshoff, Mike Hansen: Sage 3.1.2.alpha3: benchmark.py runs Maple tests that should be optional [Reviewed by David Joyner] #4027: Martin Albrecht: Sage 3.1.2.alpha3: matrix_mod2_dense.pyx doctest failure on 32 bits [Reviewed by Michael Abshoff] #4028: Mike Hansen: doctest and improve sage/interfaces/axiom.py [Reviewed by Michael Abshoff] #4030: Jason Merrill: Vectors of callable things should be callable [Reviewed by Mike Hansen] #4031: Jason Merrill: Callable symbolic expressions should allow keyword args [Reviewed by Mike Hansen] #4032: Michael Abshoff: Add x86 Solaris build support for libSingular [Reviewed by Martin Albrecht] #4033: Michael Abshoff: disabled libiconv on Solaris for the r.spkg [Reviewed by Martin Albrecht] #4034: Michael Abshoff: Fix rubiks.spkg build on Solaris [Reviewed by Martin Albrecht] #4037: Alex Ghitza: list_of_first_n() broken in interact.py [Reviewed by John Cremona] --~--~-~--~~~---~--~~ 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/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Final stretch for 3.1.2 reviews
On Sep 2, 6:43 am, John Cremona [EMAIL PROTECTED] wrote: Hi John, I hope I didn't kill #1115's chances by relabelling it from a bug fix to an enhancement, since I didn't just fix the bug... Nope, code from that area is high level and usually does introduce no failures that are platform specific. And we are still pre-rc0, which will probably take 24 or so hours to get out. The only problem with the current patch is that we found a call to dumps() crashes on a 64-bit machine but is fine on a 32-bit machine. Anyone have any idea what might cause that? No clue. Can you do a sage -ba on the tree and see of the problem goes away? What does the backtrace from gdb say? Are there any weak references involved in that code? We have been seeing oddities with weak references and Cython. John Cheers, Michael --~--~-~--~~~---~--~~ 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/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.1.2.alpha4 released
On Sep 2, 9:20 am, John Cremona [EMAIL PROTECTED] wrote: Build reports Hi John, 32-bit: just the already known failures: sage -t devel/sage/sage/stats/hmm/chmm.pyx sage -t devel/sage/sage/stats/hmm/hmm.pyx sage -t devel/sage/sage/interfaces/gp.py on Linux version 2.6.24-19-generic ([EMAIL PROTECTED]) (gcc version 4.2.3 (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Wed Aug 20 22:56:21 UTC 2008 ok, those are all known failures with tickets. 64-bit: just one failure: sage -t devel/sage/sage/interfaces/lisp.py on Linux version 2.6.18.8-0.3-default ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP Tue Apr 17 08:42:35 UTC 2007 which I think is also in Michael's list of known issues. Yes, it does not have a ticket number yet, but will do so shortly. John Cheers, Michael --~--~-~--~~~---~--~~ 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/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: reopening Sage - Blender discussion
On Sep 2, 10:40 pm, mhampton [EMAIL PROTECTED] wrote: Thanks very much for this response. ffmpeg looks very useful to me, I am checking it out right now. It is unclear to me what the overlap is with mplayer/mencoder. It seems that ffmpeg is somewhat leaner and more portable, so I am thinking of using it as the encoder for your first suggestion (create a sequence of jpegs with the tachyon raytracer, then convert to mp4). ffmpeg seems quite fast to me compared to using imagemagick with GIFs. You may be able to get some useful ideas from a video io package someone wrote for matlab that uses ffmpeg: http://www.mathworks.com/matlabcentral/fileexchange/loadFile.do?objectId=15224 I haven't poked around in the internals of this at all myself, so I have no idea whether any of it is adaptable. Regards, JM --~--~-~--~~~---~--~~ 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/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.1.2.alpha4 released
On a mac intel (10.5) I had: The following tests failed: sage -t devel/sage/sage/interfaces/gp.py sage -t devel/sage/sage/interfaces/lisp.py sage -t devel/sage/sage/interfaces/sage0.py ...which look like they are all known issues. -M. Hampton On Sep 2, 7:05 pm, David Joyner [EMAIL PROTECTED] wrote: installed fine and all tests passed on amd64 hardy heron. On Tue, Sep 2, 2008 at 9:06 AM, mabshoff [EMAIL PROTECTED] wrote: Hello folks, this is alpha4 and more progress toward the final 3.1.2. As some people have noticed this release is getting larger than the original 3.1, but I guess such is life. THe m4ri issues have been sorted out, but there are still four major issues: * ghmm/hmm * gp.py doctest failing on 32 but machine * lisp/sage0 doctest failures due to issues with newlines/ipython escape character issues/synchronization * PolyBori 0.5 and ATLAS 3.8.2 still not updated. So expect rc0 with hopefully most of the above fixed. It has been a little over 2 weeks since 3.1.1, so we need to get this release out of the door. Sources and a sage.math only binary is in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.2/ Cheers, Michael Merged in Sage 3.1.alpha4: #309: Alex Ghitza: rationals enumeration not monotone in height [Reviewed by John Cremona] #1834: Alex Ghitza: General linear group over ZZ hangs in __call__ [Reviewed by John Cremona] #2547: Jason Merrill: Implement gradient(), hessian() for callable symbolic expressions [Reviewed by Mike Hansen] #3451: Alex Ghitza: inaccurate error message in scheme morphisms [Reviewed by John Cremona] #3622: Robert Bradshaw: numerical fast integration using fast float [Reviewed by Jason Merrill] #3805: Jason Merrill: sage gets basic arithmetic with sqrt(3) wrong [Reviewed by Michael Abshoff] #3921: Jason Merrill: calculus -- solve(..., constant) should complain by default [Reviewed by Alex Ghitza] #3969: Robert Brashaw: Matrix_mod2_dense hashs follow-up (see #3724)) [Reviewed by Martin Albrecht] #3974: Chris Wuthrich: renaming of integral_weierstrass_model to integral_short_weierstrass_model [Reviewed by John Cremona] #4016: Alex Ghitza: improve doctests to schemes/generic/scheme.py [Reviewed by Robert Bradshaw] #4017: Michael Abshoff: Sage 3.1.2.alpha1 - PPC OSX: numerical noise in sage/stats/hmm/chmm.pyx [Reviewed by Mike Hansen] #4018: Robert Bradshaw: casting of non t_INT pari integers [Reviewed by Alex Ghitza] #4019: Robert Bradshaw: numerator and denominator for QQ[x] [Reviewed by Alex Ghitza] #4020: Robert Bradshaw: fraction field doctests [Reviewed by Mike Hansen] #4024: Martin Albrecht: upgrade M4RI to newest upstream release (20080901) [Reviewed by Michael Abshoff] #4025: Michael Abshoff, Mike Hansen: Sage 3.1.2.alpha3: benchmark.py runs Maple tests that should be optional [Reviewed by David Joyner] #4027: Martin Albrecht: Sage 3.1.2.alpha3: matrix_mod2_dense.pyx doctest failure on 32 bits [Reviewed by Michael Abshoff] #4028: Mike Hansen: doctest and improve sage/interfaces/axiom.py [Reviewed by Michael Abshoff] #4030: Jason Merrill: Vectors of callable things should be callable [Reviewed by Mike Hansen] #4031: Jason Merrill: Callable symbolic expressions should allow keyword args [Reviewed by Mike Hansen] #4032: Michael Abshoff: Add x86 Solaris build support for libSingular [Reviewed by Martin Albrecht] #4033: Michael Abshoff: disabled libiconv on Solaris for the r.spkg [Reviewed by Martin Albrecht] #4034: Michael Abshoff: Fix rubiks.spkg build on Solaris [Reviewed by Martin Albrecht] #4037: Alex Ghitza: list_of_first_n() broken in interact.py [Reviewed by John Cremona] --~--~-~--~~~---~--~~ 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/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Syntax Highlighting for the Notebook
Live syntax highlighting for the notebook would be awesome. I'm sure it would be hard to implement, but have a look at this demonstration of codemirror: http://marijn.haverbeke.nl/codemirror/jstest.html which does live syntax highlighting for javascript in the browser. The details are pretty nice--note the automatic indentation, and what happens when you put the caret next to parentheses or curly braces. The live syntax highlighting in Mathematica 6 made it immensely more usable for me than previous versions. You can immediately see when you've spelled the name of a function incorrectly because it isn't colored the same, and you can see if you're accidentally reusing a variable that you defined earlier and then forgot about. Something for the wishlist. JM --~--~-~--~~~---~--~~ 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/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.1.2.alpha4 released
mabshoff wrote: Hello folks, this is alpha4 and more progress toward the final 3.1.2. As some people have noticed this release is getting larger than the original 3.1, but I guess such is life. THe m4ri issues have been sorted out, but there are still four major issues: * ghmm/hmm * gp.py doctest failing on 32 but machine * lisp/sage0 doctest failures due to issues with newlines/ipython escape character issues/synchronization * PolyBori 0.5 and ATLAS 3.8.2 still not updated. So expect rc0 with hopefully most of the above fixed. It has been a little over 2 weeks since 3.1.1, so we need to get this release out of the door. Sources and a sage.math only binary is in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.1.2/ On Fedora 9, 32 bits known issues: -- The following tests failed: sage -t devel/sage/sage/interfaces/lisp.py sage -t devel/sage/sage/interfaces/gp.py sage -t devel/sage/sage/interfaces/sage0.py sage -t devel/sage/sage/stats/hmm/chmm.pyx sage -t devel/sage/sage/stats/hmm/hmm.pyx Total time for all tests: 8757.4 seconds Please see /home/jaap/downloads/sage-3.1.2.alpha4/tmp/test.log for the complete log from this test. [EMAIL PROTECTED] sage-3.1.2.alpha4]$ Jaap --~--~-~--~~~---~--~~ 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/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
