[sage-devel] Re: release notes for sage-4.0

On 2-Jun-09, at 9:33 PM, Minh Nguyen wrote: > > On Sun, May 31, 2009 at 11:15 PM, Mike Hansen > wrote: >> On Sun, May 31, 2009 at 3:42 PM, William Stein >> wrote: >>> Micheal Abshoff was the only one who ever made them, so I hope you >>> can >>> figure it out. >> >> Jason Grout and I sta

[sage-devel] Re: release notes for sage-4.0

On Jun 2, 2009, at 11:42 PM, Minh Nguyen wrote: > Hi Robert, > > On Wed, Jun 3, 2009 at 6:24 AM, Robert Bradshaw > wrote: >> > > > >>> You can find a nicely formatted release tour of Sage 4.0 at >>> >>> http://mvngu.wordpress.com/2009/06/03/sage-4-0-released/ >> >> The same is up at http://wiki

[sage-devel] Re: release notes for sage-4.0

On Wed, Jun 3, 2009 at 6:38 AM, Minh Nguyen wrote: > On Wed, Jun 3, 2009 at 6:34 AM, Robert Bradshaw > wrote: >> > > > You can find a nicely formatted release tour of Sage 4.0 at http://mvngu.wordpress.com/2009/06/03/sage-4-0-released/ >>> >>> The same is up at http://wiki.sagema

[sage-devel] Re: release notes for sage-4.0

On Wed, Jun 3, 2009 at 6:34 AM, Robert Bradshaw wrote: > >>> You can find a nicely formatted release tour of Sage 4.0 at >>> >>> http://mvngu.wordpress.com/2009/06/03/sage-4-0-released/ >> >> The same is up at http://wiki.sagemath.org/sage-4.0 , right? > > Just a sec, it used to be there, and

[sage-devel] Re: release notes for sage-4.0

Hi Robert, On Wed, Jun 3, 2009 at 6:24 AM, Robert Bradshaw wrote: > >> You can find a nicely formatted release tour of Sage 4.0 at >> >> http://mvngu.wordpress.com/2009/06/03/sage-4-0-released/ > > The same is up at http://wiki.sagemath.org/sage-4.0 , right? The release tour on the Sage wiki

[sage-devel] Re: release notes for sage-4.0

On Jun 2, 2009, at 11:24 PM, Robert Bradshaw wrote: > On Jun 2, 2009, at 9:33 PM, Minh Nguyen wrote: > >> >> On Sun, May 31, 2009 at 11:15 PM, Mike Hansen >> wrote: >>> On Sun, May 31, 2009 at 3:42 PM, William Stein >>> wrote: Micheal Abshoff was the only one who ever made them, so I hope

[sage-devel] Re: release notes for sage-4.0

Dear Minh, On Jun 3, 6:33 am, Minh Nguyen wrote: > You can find a nicely formatted release tour of Sage 4.0 at > > http://mvngu.wordpress.com/2009/06/03/sage-4-0-released/ Great job! Cheers, Simon --~--~-~--~~~---~--~~ To post to this group, send email to

[sage-devel] Re: release notes for sage-4.0

On Jun 2, 2009, at 9:33 PM, Minh Nguyen wrote: > > On Sun, May 31, 2009 at 11:15 PM, Mike Hansen > wrote: >> On Sun, May 31, 2009 at 3:42 PM, William Stein >> wrote: >>> Micheal Abshoff was the only one who ever made them, so I hope >>> you can >>> figure it out. >> >> Jason Grout and I s

[sage-devel] Re: release notes for sage-4.0

On Sun, May 31, 2009 at 11:15 PM, Mike Hansen wrote: > On Sun, May 31, 2009 at 3:42 PM, William Stein wrote: >> Micheal Abshoff was the only one who ever made them, so I hope you can >> figure it out. > > Jason Grout and I started them.  You can find them at > http://sage.math.washington.edu/hom

[sage-devel] Re: include a simplejson spkg?

On Tue, 02 Jun 2009 at 10:51PM -0300, Gonzalo Tornaria wrote: > On Tue, Jun 2, 2009 at 2:40 AM, Dan Drake wrote: > > The patches at #5564 need a json encoder, and there's a ticket to > > include simplejson at #1510. I'd like to get this spkg in, but there are > > The ticket #5564 is still lacking

[sage-devel] Re: include a simplejson spkg?

William Stein wrote: > On Tue, Jun 2, 2009 at 6:14 PM, Nick Alexander wrote: >> >> On 2-Jun-09, at 5:59 PM, Dan Drake wrote: >> >>> On Tue, 02 Jun 2009 at 09:16AM -0700, Nick Alexander wrote: > Note that Python 2.6 includes a JSON module by default, so we might > have to deal with these i

[sage-devel] Re: include a simplejson spkg?

On Tue, Jun 2, 2009 at 2:40 AM, Dan Drake wrote: > The patches at #5564 need a json encoder, and there's a ticket to > include simplejson at #1510. I'd like to get this spkg in, but there are The ticket #5564 is still lacking a description of the problem the (quite long) patches are actually solv

[sage-devel] Re: include a simplejson spkg?

On Tue, 02 Jun 2009 at 02:33PM -0400, didier deshommes wrote: > I think you have to define dump(), and save() method for custom > classes. There is a way to do it here (from the py2.6 docs): > http://docs.python.org/library/json.html > > You basically have to subclass JSONEncoder/Decoder. Well, s

[sage-devel] Re: include a simplejson spkg?

On Tue, Jun 2, 2009 at 6:14 PM, Nick Alexander wrote: > > > On 2-Jun-09, at 5:59 PM, Dan Drake wrote: > >> On Tue, 02 Jun 2009 at 09:16AM -0700, Nick Alexander wrote: Note that Python 2.6 includes a JSON module by default, so we might have to deal with these issues sooner or later anywa

[sage-devel] Re: include a simplejson spkg?

On Jun 2, 2009, at 6:14 PM, Nick Alexander wrote: > On 2-Jun-09, at 5:59 PM, Dan Drake wrote: > >> On Tue, 02 Jun 2009 at 09:16AM -0700, Nick Alexander wrote: Note that Python 2.6 includes a JSON module by default, so we might have to deal with these issues sooner or later anyway. >>> >

[sage-devel] Re: include a simplejson spkg?

On 2-Jun-09, at 5:59 PM, Dan Drake wrote: > On Tue, 02 Jun 2009 at 09:16AM -0700, Nick Alexander wrote: >>> Note that Python 2.6 includes a JSON module by default, so we might >>> have to deal with these issues sooner or later anyway. >> >> Why are we not using this? (Or a version backported to

[sage-devel] Re: include a simplejson spkg?

On Tue, 02 Jun 2009 at 09:16AM -0700, Nick Alexander wrote: > > Note that Python 2.6 includes a JSON module by default, so we might > > have to deal with these issues sooner or later anyway. > > Why are we not using this? (Or a version backported to Python 2.5, if > that would be needed?) The

[sage-devel] Re: Sage 4.0.1.alpha0 released!

On Jun 1, 2009, at 09:32 , Mike Hansen wrote: > > Hello, > > Sage 4.0.1.alpha has been released. This should hopefully take care > of > the rest of the fallout from the switch to Pynac. The tarball can be > found at > > http://sage.math.washington.edu/home/mhansen/sage-4.0.1.alpha0.tar > > a

[sage-devel] Re: Sage 4.0.1.alpha0 released!

On Jun 2, 7:59 am, davidloeffler wrote: > \begin{grumble} > > For me, 4.0.1.alpha0 builds successfully on 32-bit Linux (upgrading > from 4.0). But there are a bunch of errors building the reference > manual, coming from sage.combinat.backtrack.SearchForest. This is > rather frustrating given th

[sage-devel] Re: Release Management

Hi Georg, On Wed, Jun 3, 2009 at 6:01 AM, gsw wrote: > > Since (the Sage review process and) the Sage release process have been > pretty stable for more than a year now, this should go right into a > new chapter in the Sage Development Guide. (IIRC Minh already has > compiled some notes there

[sage-devel] Re: Release Management

Hi, a "Configuration Management Plan" would be quite helpful (fancy wording from professional software development). In down-to-earth terms, (and with a grain of salt) this would be a check-list "first you do this ..., remember always to ..., then you do that ..., and don't you forget to ..., an

[sage-devel] jQuery Plug-ins List

Hi, I ran across this web site listing various jQuery plug-ins: http://jquerylist.com/ I thought it might come in handy for notebook development. Cheers, Tim. --- Tim Lahey PhD Candidate, Systems Design Engineering University of Waterloo http://www.linkedin.com/in/timlahey --~--~-~-

[sage-devel] Re: include a simplejson spkg?

On Tue, Jun 2, 2009 at 1:40 AM, Dan Drake wrote: > The patches at #5564 need a json encoder, and there's a ticket to > include simplejson at #1510. I'd like to get this spkg in, but there are > some comments on that ticket about pickling. I don't know enough of the > details, so I thought I would

[sage-devel] Re: Sage 4.0.1.alpha0 released!

On Tue, Jun 2, 2009 at 8:35 AM, kcrisman wrote: > >> > Come on, guys; is it really so hard to run "sage -docbuild reference >> > html" and check the output before you submit (or give a positive >> > review to) a patch? >> >> > \end{grumble} >> >> I've added this to the patch review guidelines: >>

[sage-devel] Re: Sage 4.0.1.alpha0 released!

On Jun 2, 9:06 am, John Cremona wrote: > 2009/6/2 davidloeffler : > > > What does force a complete rebuild is making a new branch with "sage - > > clone". This is annoying; I don't know enough about the build > > machinery to know if this can be changed. > > I agree.  If I have built the docs in

[sage-devel] sage vmware

I have two questions about the VMware version of Sage: 1. On my Windows XP laptop (Dell Latitude D620), when I shut down the VMware player there is a loud beep that occurs even if the sound is turned off (via the XP software switch). Probably this occurs because the virtual machine runs outside o

[sage-devel] Re: include a simplejson spkg?

> Note that Python 2.6 includes a > JSON module by default, so we might have to deal with these issues > sooner or later anyway. Why are we not using this? (Or a version backported to Python 2.5, if that would be needed?) Nick --~--~-~--~~~---~--~~ To post to

[sage-devel] Re: Sage 4.0.1.alpha0 released!

2009/6/2 davidloeffler : > > On Jun 2, 4:35 pm, kcrisman wrote: >> >> Though I'll point out, for the sake of argument, that some of us have >> such underpowered computers that even running full doctests is not >> practical (i.e. everything times out), and given how long it takes to >> build the d

[sage-devel] Re: Release Management

>> Should we start a "sage-release" mailing list for planning releases >> and discussing build issues? > > Personally, I like it if it sticks here on sage-devel. We could tag > each subject by a scheme, like in trac, so that we know it is about > release management. e.g. "[release x.y.z]". And if

[sage-devel] Re: bug in plot3d?

Here is another strange plot3d behavior (taken from the plot3d docstring and slightly modified): sage: plot3d(lambda x, y: x^2 + y^2, (-2,2), (-2,2)) # works as expected but sage: plot3d(lambda x, y: x^2 + y^2, (0,2), (0,2)) # throws an exception Traceback (most recent call last): File ""

[sage-devel] Re: Sage 4.0.1.alpha0 released!

On Jun 2, 4:35 pm, kcrisman wrote: > > Though I'll point out, for the sake of argument, that some of us have > such underpowered computers that even running full doctests is not > practical (i.e. everything times out), and given how long it takes to > build the documentation whenever I even upgra

[sage-devel] Re: Sage 4.0.1.alpha0 released!

> > Come on, guys; is it really so hard to run "sage -docbuild reference > > html" and check the output before you submit (or give a positive > > review to) a patch? > > > \end{grumble} > > I've added this to the patch review guidelines: > > http://wiki.sagemath.org/TracGuidelines#ReviewingPatches

[sage-devel] Findings

Hello, I have to fill out an NSF annual report about sage.math (and related hardware) ASAP.If you have used the hardware to accomplish anything that could possibly be described as a "research finding", could you please email it to me. A simple plain text bullet point sentence, e.g., * C

[sage-devel] Re: Release Management

On Jun 2, 9:12 am, William Stein wrote: > Since Michael has mentioned that he's going to be stepping down as > release manage... I would like to add, that we probably need to organize us a bit more. For example, when do we post on sage-announce 4.0? ... etc. (website and mirrors are ready for a

[sage-devel] Re: Sage 4.0 calling undefined functions

On Tue, Jun 2, 2009 at 6:32 AM, Jerome Lefebvre wrote: > > Hello, > > Two function call that access other functions that aren't defined. Thanks. This now trac #6186: http://trac.sagemath.org/sage_trac/ticket/6186 > > sage: version() > 'Sage Version 4.0, Release Date: 2009-05-29' > > sage:

[sage-devel] Re: Sage 4.0.1.alpha0 released!

On Tue, Jun 2, 2009 at 7:59 AM, davidloeffler wrote: > > \begin{grumble} > > For me, 4.0.1.alpha0 builds successfully on 32-bit Linux (upgrading > from 4.0). But there are a bunch of errors building the reference > manual, coming from sage.combinat.backtrack.SearchForest. This is > rather frustra

[sage-devel] Graphs in Sage need referee!

Hello, I desperately need someone to start looking over the patches on #6085. I am finishing the c_graph implementation so that Cython can replace NetworkX (which is written in Python) to increase performance. There may be another patch or two, but there is already plenty to look at. My goal for

[sage-devel] Re: Sage 4.0.1.alpha0 released!

\begin{grumble} For me, 4.0.1.alpha0 builds successfully on 32-bit Linux (upgrading from 4.0). But there are a bunch of errors building the reference manual, coming from sage.combinat.backtrack.SearchForest. This is rather frustrating given the hours of work I put in to making sure the 4.0 docs b

[sage-devel] Re: Sage 4.0.1.alpha0 released!

William Stein wrote: > Mike wisely removed the README.txt from spkg/standard/, since it was > just an out of date version of the README in SAGE_ROOT. I've just put > back a simple 1-linear README.txt in spkg/standard/ (in mike's > account). Can you try the upgrade again? > On Fedora 9, 32 bit

[sage-devel] Sage 4.0 calling undefined functions

Hello, Two function call that access other functions that aren't defined. sage: version() 'Sage Version 4.0, Release Date: 2009-05-29' sage: G = Algebras(CC); G.category() --- NameError Trac

[sage-devel] Re: Sage 4.0.1.alpha0 released!

Hi Vlad, I've had similar problems with compiling sage-4.0 using gcc 4.4.0 in archlinux. I had to downgrade my gcc to 4.3.3, and now sage is compiling fine. Best, Alex On Tue, Jun 2, 2009 at 9:55 PM, prhlava wrote: > > > Hello, > >> http://sage.math.washington.edu/home/mhansen/sage-4.0.1.alp

[sage-devel] Re: Sage 4.0.1.alpha0 released!

For some reason, it now seems very difficult to quit the notebook with 4.0.1.alpha: ^C2009-06-02 07:17:02-0500 [-] Saving notebook... ^C2009-06-02 07:20:20-0500 [-] Saving notebook... ^C^C ...usually I just have to wait a few seconds. -Marshall On Jun 1, 11:32 am, Mike Hansen wrote: > Hello,

[sage-devel] Re: bug in plot3d?

I have given a positive review. I didn't do a huge amount of testing but it seems like a very straightforward patch. -Marshall On Jun 2, 3:34 am, William Cauchois wrote: > A fix is up at , and > needs a review! > > On Mon, Jun 1, 2009 at 12:51 AM

[sage-devel] Re: Sage 4.0.1.alpha0 released!

Hello, > http://sage.math.washington.edu/home/mhansen/sage-4.0.1.alpha0.tar I have tried to compile this under ArchLinux (32 bit) with: gcc (GCC) 4.4.0 20090526 (prerelease) glibc 2.10.1-2 And the compilation stops with error in singular: make install in kernel make[4]: Entering directory `

[sage-devel] Re: Release Management

Personally I would prefer that release coordination be done on sage- devel, rather than a seperate mailing list. But I am probably in a minority of how I interact with such things (I only read these on the web, not email for example). Maybe some day there could be a sage days devoted to releases

[sage-devel] Re: Release Management

On Tue, Jun 2, 2009 at 3:12 AM, William Stein wrote: > > Hello Sage-Devel, > > Since Michael has mentioned that he's going to be stepping down as > release manager, we're going to distribute the work of release > management on a rotating basis. Many Sage developers are ready to do > release manag

[sage-devel] Re: bug in plot3d?

A fix is up at , and needs a review! On Mon, Jun 1, 2009 at 12:51 AM, William Cauchois wrote: > I looked into this, and I found that the mesh=True property is > supposed to be passed via RenderParams to jmol_repr(). However, this > isn't happening.

[sage-devel] Release Management

Hello Sage-Devel, Since Michael has mentioned that he's going to be stepping down as release manager, we're going to distribute the work of release management on a rotating basis. Many Sage developers are ready to do release management, including Mike Hansen, Martin Albrecht, Robert Miller, Craig

Fwd: [sage-devel] A command line feature - operate and get next history line

-- Forwarded message -- From: Fernando Perez Date: Mon, Jun 1, 2009 at 11:31 PM Subject: Re: [sage-devel] A command line feature - operate and get next history line To: William Stein Hi William, On Thu, May 28, 2009 at 5:07 PM, William Stein wrote: > -- Forwarded mess