[sage-devel] typos on Sage's download-packages.html

Hi folks, At the site http://www.sagemath.org/download-packages.html I notice a possible typo. For the interested maintainer, here's a diff: -Please have look at the Sage Wiki tracking SPKGs. +Please have a look at the Sage Wiki tracking SPKGs. -- Regards, Minh Van Nguyen Web: http://nguyen

[sage-devel] typos on Sage links page

Hi folks, At the site http://www.sagemath.org/links.html I notice a possible typo. Here's a diff for anyone who manages that site: -Sage uses Sphinx to generate beatiful Python code documentations. +Sage uses Sphinx to generate beautiful Python code documentations. -- Regards, Minh Van Nguye

[sage-devel] Re: one of you should review this -- it's easy; rainier from msr ran into this problem today

Em Sáb, 2008-11-15 às 15:56 -0800, mabshoff escreveu: > > > On Nov 15, 3:18 pm, Ronan Paixão <[EMAIL PROTECTED]> wrote: > > Hi, > > > I have recently opened up a page about getting started in Sage > > development in the wiki, as a suggestion from William > > > > http://wiki.sagemath.org/HowToB

[sage-devel] Re: Sage 3.2.rc1 released

On Nov 15, 2008, at 15:39 , mabshoff wrote: > > > > On Nov 15, 3:36 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > > > >> Built w/o problems on Mac OS X, 10.5.5 (Dual Quad Xeon). Testing >> showed two failures, as follows. Should I file bug reports? > > Both are known failures with ticke

[sage-devel] Re: Contributing to Sage

Tnx for the kickstart. I'm working through the python tutorial now. --~--~-~--~~~---~--~~ 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://gr

[sage-devel] Re: one of you should review this -- it's easy; rainier from msr ran into this problem today

On Nov 15, 3:01 pm, mabshoff <[EMAIL PROTECTED]> wrote: > On Nov 15, 2:56 pm, "Georg S. Weber" <[EMAIL PROTECTED]> > wrote: > > > > > But I don't think I open a ticket for this unless I have some lines, > > say at least a first draft for some third chapter of  the prgramming > > doc. > > The new

[sage-devel] Re: one of you should review this -- it's easy; rainier from msr ran into this problem today

On Nov 15, 3:18 pm, Ronan Paixão <[EMAIL PROTECTED]> wrote: Hi, > I have recently opened up a page about getting started in Sage > development in the wiki, as a suggestion from William > > http://wiki.sagemath.org/HowToBeginSageDevelopment > > following a discussion on how a newbie should star

[sage-devel] Re: Sage 3.2.rc1 released

On Nov 15, 3:36 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > Built w/o problems on Mac OS X, 10.5.5 (Dual Quad Xeon).  Testing   > showed two failures, as follows.  Should I file bug reports? Both are known failures with tickets, so no need to do anything besides fixing them :) > Jus

[sage-devel] Re: Sage 3.2.rc1 released

On Nov 15, 2008, at 03:15 , mabshoff wrote: > > Hello folks, > > here goes the slightly delayed 3.2.rc1 with some goodies from SD 11 as > well as various fixes from Bug Day 16. There are actually *four* > segfault fixes in this build. On top the cleanup up build system, i.e. > massive speedups t

[sage-devel] Re: one of you should review this -- it's easy; rainier from msr ran into this problem today

I have recently opened up a page about getting started in Sage development in the wiki, as a suggestion from William http://wiki.sagemath.org/HowToBeginSageDevelopment following a discussion on how a newbie should start Sage development. Maybe the ticket flow information should get there. I hav

[sage-devel] Re: Sage 3.2.rc1 released

Hi, on Intel Mac OS X 10.4.11 / XCode 2.5 only three of these: On 15 Nov., 21:07, John H Palmieri <[EMAIL PROTECTED]> wrote: > On intel mac running 10.5, four tests failed with sage -testall -long, > all of which are known issues: > > wester.py numerical noise

[sage-devel] Re: one of you should review this -- it's easy; rainier from msr ran into this problem today

On Nov 15, 2:56 pm, "Georg S. Weber" <[EMAIL PROTECTED]> wrote: > But I don't think I open a ticket for this unless I have some lines, > say at least a first draft for some third chapter of  the prgramming > doc. The new info should either go into the Developers documentation or into the wik

[sage-devel] Re: one of you should review this -- it's easy; rainier from msr ran into this problem today

Well. Sigh. I went through this myself only very recently, so I understand the question(s). Of course we have http://wiki.sagemath.org/TracGuidelines which already helps a lot, and http://sagetrac.org/sage_trac/ where also very valuable information is recorded, and links from http://www.s

[sage-devel] Re: one of you should review this -- it's easy; rainier from msr ran into this problem today

I am posting this to sage-Devel where it belongs... On 11/15/08, Dan Shumow <[EMAIL PROTECTED]> wrote: >>> Is there a doc for all this trac review process stuff? Or is it just >>> oral history? >> >> Some doc in the wiki, but most of the other stuff is oral. What >> exactly do you want to know? >

[sage-devel] Re: Contributing to Sage

> This is a pretty nice description of how to get into development. > Ronan, I encourage you to submit a patch to the > developer guide with some text as above. At the least, put > something like that on the wiki. > > William Done. http://wiki.sagemath.org/HowToBeginSageDevelopment Ronan -

[sage-devel] Re: Sage 3.2.rc1 released

All tests passed gutsy x86_64 On Nov 15, 3:15 am, mabshoff <[EMAIL PROTECTED]> wrote: > Hello folks, > > here goes the slightly delayed 3.2.rc1 with some goodies from SD 11 as > well as various fixes from Bug Day 16. There are actually *four* > segfault fixes in this build. On top the cleanup up

[sage-devel] Re: Sage 3.2.rc1 released

2008/11/15 mabshoff <[EMAIL PROTECTED]>: > > > > On Nov 15, 8:25 am, "John Cremona" <[EMAIL PROTECTED]> wrote: >> I had one doctest failure on a 32-bit ubuntu laptop: >> >> sage -t devel/sage/sage/combinat/species/library.py >> *

[sage-devel] Re: Sage 3.2.rc1 released

On Nov 15, 12:25 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: Hi Jaap, > This was already in rc0: Yes, I do remember, but we did not open a ticket then :) > Jaap Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroup

[sage-devel] Re: Sage 3.2.rc1 released

mabshoff wrote: > > > On Nov 15, 8:25 am, "John Cremona" <[EMAIL PROTECTED]> wrote: >> I had one doctest failure on a 32-bit ubuntu laptop: >> >> sage -t devel/sage/sage/combinat/species/library.py >> ** >> File "/home/john/sag

[sage-devel] Re: Contributing to Sage

On Sat, Nov 15, 2008 at 8:55 AM, Ronan Paixão <[EMAIL PROTECTED]> wrote: > > As for myself, I'm also just starting sage development, which is also my > first not-just-myself-as-dev-team project I work for. > > If you don't know python, you should start there, since it's sage's main > language. I c

[sage-devel] Re: Sage 3.2.rc1 released

On Nov 15, 8:25 am, "John Cremona" <[EMAIL PROTECTED]> wrote: > I had one doctest failure on a 32-bit ubuntu laptop: > > sage -t  devel/sage/sage/combinat/species/library.py > ** > File "/home/john/sage-3.2.rc1/devel/sage/sage/c

[sage-devel] Re: Sage 3.2.rc1 released

On intel mac running 10.5, four tests failed with sage -testall -long, all of which are known issues: wester.py numerical noise matrix_double_dense numerical noise sr.py out of memory

[sage-devel] Re: Log scale in plot

Em Sex, 2008-11-14 às 16:22 -0200, Ronan Paixão escreveu: > I recently thought about implementing more functions used by non-math > people (I'm an Electronic Engineering student). > > I started by trying to make a Bode plot, but after a lot of digging to > find how to make subplots and how to us

[sage-devel] Re: Sage 3.2.rc1 released

John Cremona wrote: > I had one doctest failure on a 32-bit ubuntu laptop: > > sage -t devel/sage/sage/combinat/species/library.py > ** > File "/home/john/sage-3.2.rc1/devel/sage/sage/combinat/species/library.py", > line 86: >

[sage-devel] Re: Emacs and Sage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 mabshoff wrote: > > > On Nov 15, 9:49 am, Thomas Kahle <[EMAIL PROTECTED]> wrote: > Hi, > > has anyone ever programmed / requested / thought about an emacs-mode for > sage. > They way I write python code is, to use to use emacs-mode (the one > comi

[sage-devel] Re: Emacs and Sage

On Nov 15, 9:49 am, Thomas Kahle <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > has anyone ever programmed / requested / thought about an emacs-mode for > sage. > They way I write python code is, to use to use emacs-mode (the one > coming with the python

[sage-devel] Emacs and Sage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, has anyone ever programmed / requested / thought about an emacs-mode for sage. They way I write python code is, to use to use emacs-mode (the one coming with the python distribution). It has syntax highlighting, tab-completion, definition lookup,

[sage-devel] Re: Best way to package code written in SAGE

On Nov 15, 4:50 am, Martin Albrecht <[EMAIL PROTECTED]> wrote: > WWMD (What Would Magma Do) ;-) Excellent. Have you just posted the T shirt slogan fro SD 12? > Cheers, > Martin Cheers, Michael > -- > name: Martin Albrecht > _pgp:http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC9

[sage-devel] Re: Contributing to Sage

As for myself, I'm also just starting sage development, which is also my first not-just-myself-as-dev-team project I work for. If you don't know python, you should start there, since it's sage's main language. I can't say that I'm a pro coder in any language, but I would suggest you start by the

[sage-devel] Re: Sage 3.2.rc1 released

I had one doctest failure on a 32-bit ubuntu laptop: sage -t devel/sage/sage/combinat/species/library.py ** File "/home/john/sage-3.2.rc1/devel/sage/sage/combinat/species/library.py", line 86: sage: a.automorphism_group() Ex

[sage-devel] Contributing to Sage

William asked me to post the following on the sage-devel list. Could someone here help me get started? Kind Regards >> > Some help in where to start would also be apreciated (this is the first >> > open >> > source developement project that I'm interested in joining so I read >>

[sage-devel] Re: Best way to package code written in SAGE

2008/11/15 Martin Albrecht <[EMAIL PROTECTED]>: > > On Saturday 15 November 2008, David Møller Hansen wrote: >> The pairing is 'just' a bilinear mapping of two point in a curve group >> into a "third" group, type depending on what pairing. >> >> I'm wondering where pairings should go in Sage struc

[sage-devel] Re: Best way to package code written in SAGE

On Saturday 15 November 2008, David Møller Hansen wrote: > The pairing is 'just' a bilinear mapping of two point in a curve group > into a "third" group, type depending on what pairing. > > I'm wondering where pairings should go in Sage structure? > > - any comments on that? WWMD (What Would Magm

[sage-devel] Sage 3.2.rc1 released

Hello folks, here goes the slightly delayed 3.2.rc1 with some goodies from SD 11 as well as various fixes from Bug Day 16. There are actually *four* segfault fixes in this build. On top the cleanup up build system, i.e. massive speedups to dependency tracking and cleanups of setup.py, are in and

[sage-devel] Re: symbolic summation interface

On Nov 14, 2008, at 10:17 AM, Robert Bradshaw wrote: > On Nov 14, 2008, at 7:05 AM, Jason Grout wrote: > >> Mike Hansen wrote: >>> Hello, >>> >>> On Nov 14, 12:26 am, Jason Grout <[EMAIL PROTECTED]> >>> wrote: Franco Saliola wrote: >> Any comments or objections? > What about l

[sage-devel] Re: ticket #4499 merged in Sage 3.1.rc1?

On Nov 15, 12:38 am, "Minh Nguyen" <[EMAIL PROTECTED]> wrote: > Hi folks, > > Maybe it's my lack of sleep, but am I actually seeing the following > line for #4499? > > "Merged in Sage 3.1.rc1" It is a typo and obviously 3.2.rc1. > -- > Regards > Minh Van Nguyen > > Web:http://nguyenminh2.googl

[sage-devel] ticket #4499 merged in Sage 3.1.rc1?

Hi folks, Maybe it's my lack of sleep, but am I actually seeing the following line for #4499? "Merged in Sage 3.1.rc1" -- Regards Minh Van Nguyen Web: http://nguyenminh2.googlepages.com Blog: http://mvngu.wordpress.com --~--~-~--~~~---~--~~ To post to this gro

[sage-devel] Re: Best way to package code written in SAGE

The pairing is 'just' a bilinear mapping of two point in a curve group into a "third" group, type depending on what pairing. I'm wondering where pairings should go in Sage structure? - any comments on that? On 14 Nov., 19:38, Burcin Erocal <[EMAIL PROTECTED]> wrote: > On Fri, 14 Nov 2008 14:10: