[sage-devel] Re: Doc rendering improvement suggestions.

On 11/13/2009 09:42 PM, John H Palmieri wrote: > I like this. (Note, though, that it doesn't show all of the methods > for chain complexes (for instance) in one place, and it doesn't let > you easily see which ones from SageObject may have been overridden.) On including inherited members but not

[sage-devel] Re: Notebook tickets to close or combine?

By the way, I started with this list: http://trac.sagemath.org/sage_trac/query?status=needs_info&status=needs_review&status=needs_work&status=new&max=200&component=notebook&order=id&col=id&col=summary&col=component&col=type&col=status&col=priority&col=milestone These are all open "notebook" comp

[sage-devel] Notebook tickets to close or combine?

I apologize for misinterpreting a ticket. Absolutely no offense is intended. There may be others on Trac that I've missed. Format: (Summary, URL)+, suggested resolution. notebook -- change it so worksheet text is *not* stored in the notebook/worksheet objects when pickling and unpickling http

[sage-devel] Re: citations in sphinx/rest

On Nov 13, 2009, at 9:53 PM, Alex Ghitza wrote: > Hi, > > Martin Albrecht pointed out to me that there is a way to markup > citations and references in ReST (and that I should be using that in > my patches). I was so happy to see this that I immediately fixed my > patch and added a few words to

[sage-devel] Re: google wave invites

ok i'm out of invites. On Nov 12, 9:29 pm, clinton bowen wrote: > I have 2 invites left.  Email me asap with the subject > "Sage-devel:GoogleWaveInvite". > > Thanks > > On Nov 9, 3:44 am, Dan Drake wrote: > > > On Mon, 09 Nov 2009 at 10:46AM +0100, Harald Schilly wrote: > > > hi, i have manygo

[sage-devel] citations in sphinx/rest

Hi, Martin Albrecht pointed out to me that there is a way to markup citations and references in ReST (and that I should be using that in my patches). I was so happy to see this that I immediately fixed my patch and added a few words to the developer guide to this effect (see http://trac.sagemat

[sage-devel] Re: Graphical Physics Program Suggestions

On Nov 13, 7:44 pm, William Stein wrote: > On Fri, Nov 13, 2009 at 5:09 PM, kstueve wrote: > > > To sage-dev > > Can someone please explain to me what traits are in the context of > > tvisual?  The wiki page for it (http://www.enthought.com/traitsfrom > > the pagehttps://svn.enthought.com/enth

[sage-devel] Re: Doc rendering improvement suggestions.

On Nov 13, 5:36 pm, Pat LeSmithe wrote: > On 11/13/2009 04:58 PM, Florent Hivert wrote: > > > If it's doable, I think that is the good way, as I suggested: > > >  > when documenting a class, either put systematically links to the upper > >  > classes, or else put some array with inherited methods

[sage-devel] Re: Adding new functions for specific tasks related (logarithm, rational functions, ....)

On Fri, Nov 13, 2009 at 5:17 PM, kcrisman wrote: > >> Finally, one could imagine the implementation of the >> maxima_methods() function being moved to Nils Bruin's new ecl lisp >> library interface (is that refereed yet?!), > > No!  Please, please, someone who knows more about Lisp than I do > re

[sage-devel] Re: Graphical Physics Program Suggestions

On Fri, Nov 13, 2009 at 5:09 PM, kstueve wrote: > > To sage-dev > Can someone please explain to me what traits are in the context of > tvisual?  The wiki page for it (http://www.enthought.com/traits from > the page https://svn.enthought.com/enthought/wiki/TVTKIntroduction) is > a dead link. > A g

[sage-devel] Re: testing all optional spkg's

On Fri, 13 Nov 2009 at 10:53AM -0800, mhampton wrote: > It needs the glpk and 4ti2 packages, so I attempt to install them with > "sage -i" in the spkg- install script. The bad thing is I hard-code > the package numbers, so that will break if they are updated. Regarding just that issue, the patch

[sage-devel] Re: Doc rendering improvement suggestions.

On 11/13/2009 04:58 PM, Florent Hivert wrote: > If it's doable, I think that is the good way, as I suggested: > > > when documenting a class, either put systematically links to the upper > > classes, or else put some array with inherited methods together with > > links." According to http://

[sage-devel] Re: Adding new functions for specific tasks related (logarithm, rational functions, ....)

> Finally, one could imagine the implementation of the > maxima_methods() function being moved to Nils Bruin's new ecl lisp > library interface (is that refereed yet?!), No! Please, please, someone who knows more about Lisp than I do referee it! It would be a great addition to 4.3. There is r

[sage-devel] Re: Doc rendering improvement suggestions.

Hi, > > As an online document, I think the cost for repetition is almost > > nothing, and is greatly outweighed by the benefit of having these > > inherited functions explicitly listed. > > We can also *list* them without listing their docstrings. I.e., a > list (with links) to the docs o

[sage-devel] Re: Graphical Physics Program Suggestions

To sage-dev Can someone please explain to me what traits are in the context of tvisual? The wiki page for it (http://www.enthought.com/traits from the page https://svn.enthought.com/enthought/wiki/TVTKIntroduction) is a dead link. A google search of either vpython.org or svn.enthought.com produce

[sage-devel] Re: sage-grid

On Fri, Nov 13, 2009 at 4:20 PM, Minh Nguyen wrote: > > On Sat, Nov 14, 2009 at 9:48 AM, Serge A. Salamanka wrote: >> >> Hi, >> >> Is that ok to use [sage-grid] identifier for the project here: >> http://groups.google.com/group/sage-grid ? > > Not much has happened with parallel and distributed

[sage-devel] Re: testing all optional spkg's

On Fri, Nov 13, 2009 at 4:17 PM, Ralf Hemmecke wrote: > >>> Since you are *not* distributing the programs together, I don't see how >>> the GPL applies.  The *user* is the one that is running the command to >>> download the non-gpl program, and all linking or other dependencies are >>> happening

[sage-devel] Re: sage-grid

On Sat, Nov 14, 2009 at 9:48 AM, Serge A. Salamanka wrote: > > Hi, > > Is that ok to use [sage-grid] identifier for the project here: > http://groups.google.com/group/sage-grid ? Not much has happened with parallel and distributed computing using Sage. I hope that with the new group sage-grid, a

[sage-devel] Re: testing all optional spkg's

>> Since you are *not* distributing the programs together, I don't see how >> the GPL applies. The *user* is the one that is running the command to >> download the non-gpl program, and all linking or other dependencies are >> happening on the user's machine, at their request. The result is not >

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

On Fri, Nov 13, 2009 at 3:42 PM, David M. Monarres wrote: > > Thanks for the information, that is why I had asked. I have never really dug > this deep into sage before, (nor software building in general)  so I am > completely green. > > Saw this posting on macports + the output of otool -L made

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

Thanks for the information, that is why I had asked. I have never really dug this deep into sage before, (nor software building in general) so I am completely green. Saw this posting on macports + the output of otool -L made me think that this could be the problem. But I agree that it isn't

[sage-devel] Re: testing all optional spkg's

On Fri, Nov 13, 2009 at 3:26 PM, Jason Grout wrote: > > William Stein wrote: >> On Fri, Nov 13, 2009 at 11:36 AM, David Joyner wrote: >>> The solution is simple. Have two versions of a package, >>> say >>> >>> my-gpl-package.spkg >>> my-gpl-package-with-all-nongpl-dependencies-autoloaded.spkg. >

[sage-devel] Re: testing all optional spkg's

William Stein wrote: > On Fri, Nov 13, 2009 at 11:36 AM, David Joyner wrote: >> The solution is simple. Have two versions of a package, >> say >> >> my-gpl-package.spkg >> my-gpl-package-with-all-nongpl-dependencies-autoloaded.spkg. >> >> The last differs from the first only in the license and a

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

On Fri, Nov 13, 2009 at 3:18 PM, Jason Grout wrote: > > William Stein wrote: > >> I see no point at all in building ATLAS on OS X, since OS X already >> ships a highly tuned "Apple-certified" multi-core aware build of ATLAS >> systemwide.  The ATLAS's we build/ship with Sage are never multicore >

[sage-devel] Re: Doc rendering improvement suggestions.

On Fri, Nov 13, 2009 at 3:15 PM, Jason Grout wrote: > > John H Palmieri wrote: > >> This will result in a lot of repetition in the reference manual, of >> course. > > > As an online document, I think the cost for repetition is almost > nothing, and is greatly outweighed by the benefit of having t

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

William Stein wrote: > I see no point at all in building ATLAS on OS X, since OS X already > ships a highly tuned "Apple-certified" multi-core aware build of ATLAS > systemwide. The ATLAS's we build/ship with Sage are never multicore > aware. It's simply much better as far as I can tell for Sag

[sage-devel] Re: Graphical Physics Program Suggestions

Tom, Thanks. I just bought Hibbeler's "Engineering Mechanics: Statics" and "Engineering Mechanics: Dynamics" on Amazon. I saved 99% (and spent $1.57 + 2 * 3.99) because I bought old editions. Kevin Stueve On Sep 22, 2:25 pm, Tom Boothby wrote: > I spent a while thinking that I was going to b

[sage-devel] Re: Doc rendering improvement suggestions.

John H Palmieri wrote: > This will result in a lot of repetition in the reference manual, of > course. As an online document, I think the cost for repetition is almost nothing, and is greatly outweighed by the benefit of having these inherited functions explicitly listed. Jason --~--~-

[sage-devel] Re: sage-grid

William Stein пишет: > On Fri, Nov 13, 2009 at 2:48 PM, Serge A. Salamanka wrote: >> Hi, >> >> Is that ok to use [sage-grid] identifier for the project here: >> http://groups.google.com/group/sage-grid ? >> >>> Scientific Grid Computing in Sage >>> >>> Sage is a free mathematics software packag

[sage-devel] Re: sage-grid

On Fri, Nov 13, 2009 at 2:48 PM, Serge A. Salamanka wrote: > > Hi, > > Is that ok to use [sage-grid] identifier for the project here: > http://groups.google.com/group/sage-grid ? > >> Scientific Grid Computing in Sage >> >> Sage is a free mathematics software package. It combines the power of man

[sage-devel] Re: testing all optional spkg's

On Fri, Nov 13, 2009 at 2:44 PM, mhampton wrote: > > I noticed in trying this out that if a package is already installed, > > sage -c "install_package('package_name')" > > raises a ValueError, which is definitely not the behavior I'd like. > Is there a reason it does that?  Perhaps simply printin

[sage-devel] sage-grid

Hi, Is that ok to use [sage-grid] identifier for the project here: http://groups.google.com/group/sage-grid ? > Scientific Grid Computing in Sage > > Sage is a free mathematics software package. It combines the power of many > existing open-source packages into a common Python-based interface.

[sage-devel] Re: testing all optional spkg's

On Fri, Nov 13, 2009 at 2:39 PM, Ralf Hemmecke wrote: > >> Regarding: "I was told that a GPL package must not install a non-GPL >> package." >> >> The above can never legally come up, right?  If a program Foo is "GPL" >> and fundamentally depends on a program Bar that is licensed >> GPL-incompat

[sage-devel] Re: testing all optional spkg's

I noticed in trying this out that if a package is already installed, sage -c "install_package('package_name')" raises a ValueError, which is definitely not the behavior I'd like. Is there a reason it does that? Perhaps simply printing that announcement would be sufficient? -Marshall On Nov 13

[sage-devel] Re: testing all optional spkg's

On Fri, Nov 13, 2009 at 2:30 PM, Simon King wrote: > > Hi William! > > On 13 Nov., 22:46, William Stein wrote: > ... >> Regarding: "I was told that a GPL package must not install a non-GPL >> package." >> >> The above can never legally come up, right?  If a program Foo is "GPL" >> and fundament

[sage-devel] Re: testing all optional spkg's

> Regarding: "I was told that a GPL package must not install a non-GPL package." > > The above can never legally come up, right? If a program Foo is "GPL" > and fundamentally depends on a program Bar that is licensed > GPL-incompatible, then distributing Foo at all violates the GPL right? No. C

[sage-devel] Re: testing all optional spkg's

Hi William! On 13 Nov., 22:46, William Stein wrote: ... > Regarding: "I was told that a GPL package must not install a non-GPL package." > > The above can never legally come up, right?  If a program Foo is "GPL" > and fundamentally depends on a program Bar that is licensed > GPL-incompatible, th

[sage-devel] Re: testing all optional spkg's

OK, I have changed the spkg-install to use your solution. I have not tested it yet though, since I am unsure how to un-install those packages. -Marshall On Nov 13, 3:46 pm, William Stein wrote: > Regarding: "so I attempt to install them with "sage -i" in the > spkg-install script. The bad th

[sage-devel] Re: Adding new functions for specific tasks related (logarithm, rational functions, ....)

On Fri, Nov 13, 2009 at 10:12 AM, Robert Bradshaw wrote: > > On Nov 13, 2009, at 5:30 AM, Burcin Erocal wrote: > >> On Thu, 12 Nov 2009 12:30:01 -0800 (PST) >> "ma...@mendelu.cz" wrote: >> >>> Could the conclusion be the following? >>> "If you want (and if the realease manager includes correspon

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

On Fri, Nov 13, 2009 at 10:01 AM, Georg S. Weber wrote: > > > > On 13 Nov., 10:05, "David M. Monarres" wrote: >> Looking into the 'abort trap' problem and found >> >> http://trac.macports.org/ticket/20491 >> >> which relates the problem to numpy linking to a system blas/atlas. >> >> So I poked a

[sage-devel] Re: testing all optional spkg's

On Fri, Nov 13, 2009 at 11:36 AM, David Joyner wrote: > > The solution is simple. Have two versions of a package, > say > > my-gpl-package.spkg > my-gpl-package-with-all-nongpl-dependencies-autoloaded.spkg. > > The last differs from the first only in the license and a few lines of > the installer

[sage-devel] Re: testing all optional spkg's

Simon King wrote: > Hi Marshall! > > On 13 Nov., 19:53, mhampton wrote: >> I don't see why optional packages should not try to install their >> dependencies. > > The reason is the licence. Gap_packages (or at least the SmallGroups > library) is not GPL. I was told that a GPL package must not in

[sage-devel] Re: sagenb repo down?

On Fri, Nov 13, 2009 at 1:02 PM, Sameer Regmi wrote: > Hi > > The Sage Notebook HG repository site seems is down.Can I use > http://sage.math.washington.edu/home/wstein/patches/sagenb/. If yes which > file? The latest spkg is nov 12 but the latest tar.gz is 24 oct. > > Sameer > Use http://sa

[sage-devel] sagenb repo down?

Hi The Sage Notebook HG repository site seems is down.Can I use http://sage.math.washington.edu/home/wstein/patches/sagenb/. If yes which file? The latest spkg is nov 12 but the latest tar.gz is 24 oct. Sameer --~--~-~--~~~---~-

[sage-devel] Re: SageWorldMath.blip.TV

I've posted on blip.tv all the videos from Sage Days 16. Checkout http://sageworldmath.blip.tv/ One can easily syndicate the show. For example, the video player could be embedded into sagemath.org or whatever. See http://sageworldmath.blip.tv/?user=sageworldmath#syndicate I will also feature oth

[sage-devel] Re: Doc rendering improvement suggestions.

On Nov 13, 12:39 am, Florent Hivert wrote: >       Hi there, > > Here are some random suggestion about sphinx doc rendering. > Disclaimer: I've no idea how much these are doable in sphinx. > > One thing that I dislike in the current doc rendering is that the method are > reordered in alphabetical

[sage-devel] Re: testing all optional spkg's

Its at http://trac.sagemath.org/sage_trac/ticket/7453. If you want a direct link to the spkg, its at: http://sage.math.washington.edu/home/mhampton/sandpile-1.51.spkg Its missing a few things, such as a mercurial repository, but I just want to get it in as an experimental package so I didn't spe

[sage-devel] Re: testing all optional spkg's

On Fri, Nov 13, 2009 at 1:53 PM, mhampton wrote: > > I don't see why optional packages should not try to install their > dependencies.  I just made a new experimental spkg (ticket #7453) for > David Perkinson's sandpile module.  It needs the glpk and 4ti2 > packages, so I attempt to install them

[sage-devel] Re: testing all optional spkg's

The solution is simple. Have two versions of a package, say my-gpl-package.spkg my-gpl-package-with-all-nongpl-dependencies-autoloaded.spkg. The last differs from the first only in the license and a few lines of the installer script. On Fri, Nov 13, 2009 at 2:25 PM, mhampton wrote: > > Hmmm.

[sage-devel] Re: testing all optional spkg's

Hmmm. That makes sense, even though it also makes me want to bang my head on my desk. That means it should be OK if all the packages involved are GPL. There must be some variants that would also be compatible - ? -Marshall On Nov 13, 1:16 pm, Simon King wrote: > Hi Marshall! > > On 13 Nov., 19

[sage-devel] Re: testing all optional spkg's

Hi Marshall! On 13 Nov., 19:53, mhampton wrote: > I don't see why optional packages should not try to install their > dependencies. The reason is the licence. Gap_packages (or at least the SmallGroups library) is not GPL. I was told that a GPL package must not install a non-GPL package. For the

[sage-devel] Re: testing all optional spkg's

I don't see why optional packages should not try to install their dependencies. I just made a new experimental spkg (ticket #7453) for David Perkinson's sandpile module. It needs the glpk and 4ti2 packages, so I attempt to install them with "sage -i" in the spkg- install script. The bad thing i

[sage-devel] Re: Adding new functions for specific tasks related (logarithm, rational functions, ....)

On Nov 13, 2009, at 5:30 AM, Burcin Erocal wrote: > On Thu, 12 Nov 2009 12:30:01 -0800 (PST) > "ma...@mendelu.cz" wrote: > >> Could the conclusion be the following? >> "If you want (and if the realease manager includes corresponding >> patches), add support for Maxima commands which you need. Wh

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

On 13 Nov., 10:05, "David M. Monarres" wrote: > Looking into the 'abort trap' problem and found > > http://trac.macports.org/ticket/20491 > > which relates the problem to numpy linking to a system blas/atlas. > > So I poked around the blas and atlas packages and noticed that they were > disabl

[sage-devel] Re: testing all optional spkg's

> There is work being done on FriCAS at > http://trac.sagemath.org/sage_trac/ticket/6517. > The work on FriCAS-1.0.8 is a bit delayed due to troubles with the > aldor interface. I don't know what the status is but the intent is to > make two packages. Ehm... I can't remember why it shouldn't wor

[sage-devel] Re: Adding new functions for specific tasks related (logarithm, rational functions, ....)

On 13 lis, 14:30, Burcin Erocal wrote: > On Thu, 12 Nov 2009 12:30:01 -0800 (PST) > > "ma...@mendelu.cz" wrote: > > Could the conclusion be the following? > > "If you want (and if the realease manager includes corresponding > > patches), add support for Maxima commands which you need. When pytho

[sage-devel] Re: Adding new functions for specific tasks related (logarithm, rational functions, ....)

On Thu, 12 Nov 2009 12:30:01 -0800 (PST) "ma...@mendelu.cz" wrote: > Could the conclusion be the following? > "If you want (and if the realease manager includes corresponding > patches), add support for Maxima commands which you need. When python > of ginac will be able to replace these commands

[sage-devel] Re: Adding new functions for specific tasks related (logarithm, rational functions, ....)

On Thu, 12 Nov 2009 14:03:14 -0800 (PST) kcrisman wrote: > > > I like opensource software and math, but have not enough > > > knowledges to bring significant contribution in this topic. > > > > Everyone has something they can contribute: bug reports,   > > documentation, and even feature request

[sage-devel] Re: partially defining a function

On Fri, 13 Nov 2009 11:50:10 +0100 Burcin Erocal wrote: > > Hi Jason, > > On Thu, 12 Nov 2009 12:30:11 -0600 > Jason Grout wrote: > > > It would be nice if we could do something like: > > > > sage: f(x,0)=e^x > > > > sage: f(x,t)=x*t > > > > > > or > > > > sage: f(0)=0 > > sage: f(x)=si

[sage-devel] Re: testing all optional spkg's

Martin Rubey wrote: > >> NOT INSTALLED: > >> fricas-1.0.3.p0 > this is ancient! (should be 1.0.8 meanwhile) Although, I admit I have > no idea whether anybody has built a 1.0.8 package yet. Yes, it looks like that was released in June 2008 according to the Sourceforge download page. I see t

[sage-devel] Re: testing all optional spkg's

Simon King wrote: > Hi! > > Note that some optional packages fail to install due to dependencies. > For example, my p_group_cohomology-1.1.spkg requires that gap_packages > is installed first. In the log posted by David, this is given as the > reason for the failed installation. > > Is it possib

[sage-devel] Re: testing all optional spkg's

On Nov 13, 9:34 am, Martin Rubey wrote: > > NOT INSTALLED: > > fricas-1.0.3.p0 > > this is ancient!  (should be 1.0.8 meanwhile) Although, I admit I have > no idea whether anybody has built a 1.0.8 package yet. > > > 2) checking for noweave... no > > axiom_build_bindir = > > /export/home/drkirk

[sage-devel] Re: Doc rendering improvement suggestions.

Hi Florent, > One thing that I dislike in the current doc rendering is that the method are > reordered in alphabetical order. I remember I read this question in sage-devel last summer and I just found the link : http://groups.google.com/group/sage-devel/browse_thread/thread/ebbf7ebe8ebad570/3b7

[sage-devel] Re: partially defining a function

Hi Jason, On Thu, 12 Nov 2009 12:30:11 -0600 Jason Grout wrote: > It would be nice if we could do something like: > > sage: f(x,0)=e^x > > sage: f(x,t)=x*t > > > or > > sage: f(0)=0 > sage: f(x)=sin(x)/x > > Is there an elegant way to have multiple definitions like this in > pynac, or def

[sage-devel] Re: testing all optional spkg's

Hi! Note that some optional packages fail to install due to dependencies. For example, my p_group_cohomology-1.1.spkg requires that gap_packages is installed first. In the log posted by David, this is given as the reason for the failed installation. Is it possible to take care of such dependenci

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

Looking into the 'abort trap' problem and found http://trac.macports.org/ticket/20491 which relates the problem to numpy linking to a system blas/atlas. So I poked around the blas and atlas packages and noticed that they were disabled on the Darwin platform and the wisdom of this decision was

[sage-devel] Doc rendering improvement suggestions.

Hi there, Here are some random suggestion about sphinx doc rendering. Disclaimer: I've no idea how much these are doable in sphinx. One thing that I dislike in the current doc rendering is that the method are reordered in alphabetical order. It's good for reference but usually in the sour

[sage-devel] Re: testing all optional spkg's

> NOT INSTALLED: > fricas-1.0.3.p0 this is ancient! (should be 1.0.8 meanwhile) Although, I admit I have no idea whether anybody has built a 1.0.8 package yet. > 2) checking for noweave... no > axiom_build_bindir = > /export/home/drkirkby/sage-4.2/spkg/build/fricas-1.0.3.p0/build-dir/build/s

[sage-devel] Re: testing all optional spkg's

William Stein wrote: > On Thu, Nov 12, 2009 at 1:08 PM, Dr. David Kirkby > wrote: >> William Stein wrote: >>> Dave, >>> >>> I'm curious what happens if you try to install all optional spkg's on >>> solaris. >>> You could that in Sage by pasting this after the sage prompt: >> Since you do not