Re: [sage-devel] Building a deb for sage on Debian/Ubuntu

2012-02-28 Thread Jan Groenewald
Hi Dan, I want to focus on newer, and from-source, but until Friday I am only working on this from-binary. I want to add i686 today, and fix any bugs I may find. I will perhaps also try add a bug-reporting mailing list to the PPA page, it seems launchpad can host them. I may be back more often as

[sage-devel] Re: Group collaboration on a branch of Sage

2012-02-28 Thread Keshav Kini
William Stein writes: > Note that it is not obvious or documented how to effectively do this > with the Sage library with other people, and still properly submit > stuff for inclusion in Sage, but it should be possible. > > I setup something exactly like the above for trac #12545: > http://tra

[sage-devel] Re: Group collaboration on a branch of Sage

2012-02-28 Thread Keshav Kini
Jason Grout writes: > On 2/28/12 7:04 PM, David Roe wrote: >> Is there an easy way to collaborate on an experimental set of patches on >> top of Sage? The sage-combinat model is very close to what I'm looking >> for, but it seems difficult to set up all the infrastructure: we have to >> have a se

[sage-devel] Re: trac field names -- arrrrr!

2012-02-28 Thread Keshav Kini
Jason Grout writes: > On 2/28/12 5:50 PM, Michael Orlitzky wrote: >> If we require a name in the reviewer field and designate that field as >> "the person who should review the ticket," what will probably happen in >> practice is that nobody will touch tickets with a non-empty reviewer >> field, a

[sage-devel] Re: trac field names -- arrrrr!

2012-02-28 Thread kcrisman
> See above.  If the selected reviewer takes no action on a ticket after > n days, then the ticket is changed back to "needs work" (and a message > is sent) -- it is then the responsibility of the author of the ticket > to choose an active reviewer. > Huh. In sum, this sounds like the whole idea

Re: [sage-devel] Re: Group collaboration on a branch of Sage

2012-02-28 Thread William Stein
On Tue, Feb 28, 2012 at 6:04 PM, Jason Grout wrote: > On 2/28/12 7:04 PM, David Roe wrote: >> >> Is there an easy way to collaborate on an experimental set of patches on >> top of Sage?  The sage-combinat model is very close to what I'm looking >> for, but it seems difficult to set up all the infr

[sage-devel] Re: trac field names -- arrrrr!

2012-02-28 Thread William Stein
On Tue, Feb 28, 2012 at 7:31 PM, William Stein wrote: > Where is the field name "reviewer(s)" configured?   I am going to change it > to not have parens as soon as I can find it. I've figured this out via grep. > > > On Tuesday, February 28, 2012, Jason Grout > wrote: >> On 2/28/12 5:16 PM, Wil

Re: [sage-devel] Re: trac field names -- arrrrr!

2012-02-28 Thread William Stein
On Tue, Feb 28, 2012 at 7:49 PM, kcrisman wrote: > Some reasons for +1, in addition to Michael's (and I don't think that > a git switch would help much with his reasons, unless everyone had > access to the release manager's brain): >  * What about a first-time contributor to Sage of brand-new code

[sage-devel] Re: default ellipse color

2012-02-28 Thread kcrisman
On Feb 27, 2:19 pm, William Stein wrote: > On Mon, Feb 27, 2012 at 10:42 AM, William Stein wrote: > > On Mon, Feb 27, 2012 at 10:31 AM, William Stein wrote: > >> Hi, > > >> Why is the default color for an ellipse (and circle) *black*, whereas > >> the default color for (msot) everything else (

[sage-devel] Re: trac field names -- arrrrr!

2012-02-28 Thread kcrisman
On Feb 28, 8:47 pm, William Stein wrote: > On Tuesday, February 28, 2012, Keshav Kini wrote: > > Michael Orlitzky writes: > >> On 02/28/2012 06:16 PM, William Stein wrote: > >>> Incidentally, I think a ticket set to "needs review" that doesn't have > >>> a specific *reviewer* chosen by the aut

[sage-devel] Re: trac field names -- arrrrr!

2012-02-28 Thread William Stein
Where is the field name "reviewer(s)" configured? I am going to change it to not have parens as soon as I can find it. On Tuesday, February 28, 2012, Jason Grout wrote: > On 2/28/12 5:16 PM, William Stein wrote: >> >> Hi, >> >> I'm trying to make a query that lists all tickets that "needs revie

[sage-devel] Re: Build failure on Solaris 10 SPARC - cvxopt-1.1.3

2012-02-28 Thread deSitter
Also - Sage built fine with gcc 4.5.1 on my Linux installation (SuSE 11.4) -drl On Feb 28, 8:37 pm, deSitter wrote: > Sun Enterprise 420R, gcc 4.6.2, Sun linker, LD_LIBRARY_PATH=/usr/local/ > lib, Sun Studio 12 installed. > > There is a problem with inclusion of somewhere in the > cvxopt-1.1.3

[sage-devel] Re: trac field names -- arrrrr!

2012-02-28 Thread Jason Grout
On 2/28/12 5:16 PM, William Stein wrote: Hi, I'm trying to make a query that lists all tickets that "needs review", but do not have anybody in the Reviewer field. I can't do this, because the field is not "Reviewer" but "Reviewer(s)", and I can't figure out how to use the query language of trac

[sage-devel] Re: trac field names -- arrrrr!

2012-02-28 Thread Jason Grout
On 2/28/12 5:50 PM, Michael Orlitzky wrote: On 02/28/2012 06:16 PM, William Stein wrote: Incidentally, I think a ticket set to "needs review" that doesn't have a specific *reviewer* chosen by the author of the ticket, should be bumped back to "needs work". Perhaps the biggest reason we have 279

[sage-devel] Re: Group collaboration on a branch of Sage

2012-02-28 Thread Jason Grout
On 2/28/12 7:04 PM, David Roe wrote: Is there an easy way to collaborate on an experimental set of patches on top of Sage? The sage-combinat model is very close to what I'm looking for, but it seems difficult to set up all the infrastructure: we have to have a server analogous to http://sage.mat

Re: [sage-devel] Re: trac field names -- arrrrr!

2012-02-28 Thread Michael Orlitzky
On 02/28/2012 07:33 PM, Keshav Kini wrote: It's not much consolation right now, but this will become easier once we switch to git, as branches can be automatically checked for whether they are still mergeable into trunk or not. Well, the same could be done with patches I guess but it would requi

[sage-devel] Re: trac field names -- arrrrr!

2012-02-28 Thread William Stein
On Tuesday, February 28, 2012, Keshav Kini wrote: > Michael Orlitzky writes: >> On 02/28/2012 06:16 PM, William Stein wrote: >>> Incidentally, I think a ticket set to "needs review" that doesn't have >>> a specific *reviewer* chosen by the author of the ticket, should be >>> bumped back to "needs

Re: [sage-devel] Building a deb for sage on Debian/Ubuntu

2012-02-28 Thread Dan Drake
On Tue, 28 Feb 2012 at 09:50PM +0100, Jan Groenewald wrote: > The deb available below was not built from source on launchpad, instead > it is the sage upstream binary built for Ubuntu 10.04.3 hammered into a > PPA for lucid, maverick natty, oneiric, and precise in the ugliest possible > way. Three

[sage-devel] Build failure on Solaris 10 SPARC - cvxopt-1.1.3

2012-02-28 Thread deSitter
Sun Enterprise 420R, gcc 4.6.2, Sun linker, LD_LIBRARY_PATH=/usr/local/ lib, Sun Studio 12 installed. There is a problem with inclusion of somewhere in the cvxopt-1.1.3 package. Error: gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict- prototypes -fPIC -I/root/Documents/sage

[sage-devel] Group collaboration on a branch of Sage

2012-02-28 Thread David Roe
Is there an easy way to collaborate on an experimental set of patches on top of Sage? The sage-combinat model is very close to what I'm looking for, but it seems difficult to set up all the infrastructure: we have to have a server analogous to http://sage.math.washington.edu:2144/, set up the init

[sage-devel] Re: trac field names -- arrrrr!

2012-02-28 Thread Keshav Kini
Michael Orlitzky writes: > On 02/28/2012 06:16 PM, William Stein wrote: >> Incidentally, I think a ticket set to "needs review" that doesn't have >> a specific *reviewer* chosen by the author of the ticket, should be >> bumped back to "needs work". Perhaps the biggest reason we have 279 >> ticket

[sage-devel] Will a debian buildslave be usefull?

2012-02-28 Thread Maarten Derickx
Dear All, I just got my very first own server up and running, I installed debian stable (squeeze 6.0.4) on it. And I saw that sage doesn't have a buildslave for debian yet. I might want to make it available as a buildslave depending on the answers of the following questions. 1. Will it be usef

Re: [sage-devel] trac field names -- arrrrr!

2012-02-28 Thread Michael Orlitzky
On 02/28/2012 06:16 PM, William Stein wrote: Incidentally, I think a ticket set to "needs review" that doesn't have a specific *reviewer* chosen by the author of the ticket, should be bumped back to "needs work". Perhaps the biggest reason we have 279 tickets (right now) that need review is tha

[sage-devel] trac field names -- arrrrr!

2012-02-28 Thread William Stein
Hi, I'm trying to make a query that lists all tickets that "needs review", but do not have anybody in the Reviewer field. I can't do this, because the field is not "Reviewer" but "Reviewer(s)", and I can't figure out how to use the query language of trac (some sort of SQL) to deal with a field na

Re: [sage-devel] Re: Unifying Command line options

2012-02-28 Thread Michael Orlitzky
On 02/28/2012 03:45 PM, Keshav Kini wrote: William Stein writes: On Tue, Feb 28, 2012 at 8:43 AM, Keshav Kini wrote: It's not actually a fallback for b), though. If a file does exist with the same name as a subcommand, b) makes it impossible to use that subcommand without changing directory o

Re: [sage-devel] Unifying Command line options

2012-02-28 Thread William Stein
On Tuesday, February 28, 2012, Keshav Kini wrote: > William Stein writes: >> On Tue, Feb 28, 2012 at 8:43 AM, Keshav Kini wrote: >>> It's not actually a fallback for b), though. If a file does exist with >>> the same name as a subcommand, b) makes it impossible to use that >>> subcommand without

[sage-devel] Re: Unifying Command line options

2012-02-28 Thread Keshav Kini
John H Palmieri writes: > With the current setup, "foo.sage" needs to be preparsed into a Python file, > and the way Sage knows to preparse it is to recognize its extension ".sage": > see the script sage-run. I think if you do "sage foo", then it treats "foo" as > a Python file. So I guess there i

[sage-devel] Re: Unifying Command line options

2012-02-28 Thread John H Palmieri
On Tuesday, February 28, 2012 12:45:08 PM UTC-8, Keshav Kini wrote: > > William Stein writes: > > On Tue, Feb 28, 2012 at 8:43 AM, Keshav Kini wrote: > >> It's not actually a fallback for b), though. If a file does exist with > >> the same name as a subcommand, b) makes it impossible to use that

Re: [sage-devel] Building a deb for sage on Debian/Ubuntu

2012-02-28 Thread Jan Groenewald
Hi The deb available below was not built from source on launchpad, instead it is the sage upstream binary built for Ubuntu 10.04.3 hammered into a PPA for lucid, maverick natty, oneiric, and precise in the ugliest possible way. It is only 64bit at the moment. To test it do this: sudo apt-add-re

[sage-devel] Re: Unifying Command line options

2012-02-28 Thread Keshav Kini
William Stein writes: > On Tue, Feb 28, 2012 at 8:43 AM, Keshav Kini wrote: >> It's not actually a fallback for b), though. If a file does exist with >> the same name as a subcommand, b) makes it impossible to use that >> subcommand without changing directory or deleting/moving the file. One >> m

[sage-devel] Re: Preschoolers Education

2012-02-28 Thread kcrisman
On Feb 28, 5:25 am, mhampton wrote: > Scratch is great.  Its been very successful for me in introducing my > daughter to programming. > > I don't see much possible interaction with Sage, since Scratch is > written in Squeak, and it has a custom (although quite permissive) > license.  It might pr

Re: [sage-devel] Re: strange eigenvalue/eigenvector output

2012-02-28 Thread John Cremona
It's a bug in the eigenvalues() function in sage/matrix/matrix2.pyx. It takes the chapr poly, factors it, and for any factor of degree > 1 it constructs the root-field and then finds all the Galois conjugates of that in QQbar. The problem is that that gives all the conjugates over QQ, not just the

Re: [sage-devel] Re: Unifying Command line options

2012-02-28 Thread William Stein
On Tue, Feb 28, 2012 at 8:43 AM, Keshav Kini wrote: > On Tue, Feb 28, 2012 at 23:54, Michael Orlitzky wrote: >> On 02/27/12 15:51, R. Andrew Ohana wrote: >> > 2) The standard solution has been brought up, and I think it is decent >> > one; we use an escape mode with a double dash (e.g. sage -- >>

Re: [sage-devel] Re: Unifying Command line options

2012-02-28 Thread Keshav Kini
On Tue, Feb 28, 2012 at 23:54, Michael Orlitzky wrote: > On 02/27/12 15:51, R. Andrew Ohana wrote: > > 2) The standard solution has been brought up, and I think it is decent > > one; we use an escape mode with a double dash (e.g. sage -- > > some_script.sage). > > This should probably be the fallb

Re: [sage-devel] Re: Unifying Command line options

2012-02-28 Thread Michael Orlitzky
On 02/27/12 15:51, R. Andrew Ohana wrote: > > 2) How would we handle sage scripts (or other things that are truly > arguments and not subcommands) > 2) The standard solution has been brought up, and I think it is decent > one; we use an escape mode with a double dash (e.g. sage -- > some_script.s

Re: [sage-devel] Re: lzma -> xz

2012-02-28 Thread Harald Schilly
On Tue, Feb 28, 2012 at 14:59, Jan Groenewald wrote: > xz-utils provides xz, and xz-lzma provides backwards compatible commands for > lzma. ok, so then if i don't forget, it will be .xz :-) also, i just found out that fedora's rpm packages are xz compressed now (similar for debs). good to know.

Re: [sage-devel] Re: lzma -> xz

2012-02-28 Thread Jan Groenewald
Hi On 28 February 2012 14:50, Harald Schilly wrote: > > > On Monday, February 27, 2012 3:40:50 PM UTC+1, Jan Groenewald wrote: >> >> Should sage prebuilt binaries move from lzma to xz? >> > > When I started to do this, only lzma was installed as default on debian > based and fedora systems. ins

[sage-devel] Re: lzma -> xz

2012-02-28 Thread Harald Schilly
On Monday, February 27, 2012 3:40:50 PM UTC+1, Jan Groenewald wrote: > > Should sage prebuilt binaries move from lzma to xz? > When I started to do this, only lzma was installed as default on debian based and fedora systems. installing xz would have removed lzma iirc. Is xz now available on t

[sage-devel] Re: serious bug in sum

2012-02-28 Thread Harald Schilly
On Monday, February 27, 2012 2:25:58 AM UTC+1, rjf wrote: > > > If Sage were to get > GSOC approval to be a mentoring organization, would it > match mentors and students to fix bugs in Maxima? An hour ago I started a thread for project proposals. In this case I would suggest that this needs

[sage-devel] GSOC2012 Project Proposals

2012-02-28 Thread Harald Schilly
Hello! Since the other GSOC thread got a bit hijacked, I'm starting a new one. This one here is particularly only about project proposals and possible mentors. There are still some viable proposals from last year and I'll adopt them and contact the mentors directly, but it would be great to get so

[sage-devel] Re: Preschoolers Education

2012-02-28 Thread mhampton
Scratch is great. Its been very successful for me in introducing my daughter to programming. I don't see much possible interaction with Sage, since Scratch is written in Squeak, and it has a custom (although quite permissive) license. It might provide some inspiration for making some sort of vis

Re: [sage-devel] Re: Sage mini-manual in Catalan

2012-02-28 Thread John Cremona
I also forwarded this to Maite Aranes who is a Catalan speaker who has contributed to Sage. John On 28 February 2012 07:51, Georg S. Weber wrote: >  Hi, > > to my knowledge, Prof. Jordi Quer from Barcelona both speaks Catalan > and knows Sage, so he might give valuable input. If the format/ > li