[sage-devel] Re: 2D and 3D aspect ratio inconsistencies

2011-06-01 Thread kcrisman
> 3D : > === > > In 3d, the default aspect ratio is [1,1,1]. However, cube do not look like > cube: > > sage: G = cube((10,5,3)) + cube((-7,-3,0)) > sage: G.aspect_ratio() > [1.0, 1.0, 1.0] > sage: G But each one does individually: H = cube((10,5,3)) H And the other things do work on individu

[sage-devel] Re: [linbox-use] Nullspace of a rational matrix?

2011-06-01 Thread William Stein
On Wed, Jun 1, 2011 at 11:32 AM, B Saunders wrote: > >> >> When I wrote this code in 2007, for some range of matrix sizes and >> bitsizes it was the fastest code in the world (even solidly beating >> Magma, which was the fastest before)... mainly since IML is so damned >> good.   I don't know what

Re: [sage-devel] sage and python 2.7: migration strategies?

2011-06-01 Thread Paulo César Pereira de Andrade
2011/6/1 Francois Bissey : >> 2011/4/9 Francois Bissey : >> > It turns out that warnings are not visible to the end users anymore. >> > This is according to the python documentation: >> > http://docs.python.org/library/warnings.html >> > Section 27.6.5 to be precise. >> > Actually more explicit in

[sage-devel] Re: 2D and 3D aspect ratio inconsistencies

2011-06-01 Thread kcrisman
This may not be directly related, but see http://trac.sagemath.org/sage_trac/ticket/2100 for a long-standing ticket that Jason and I need to finish up - we basically just need to agree on defaults, but the patch should apply nicely, or at least used to. The default is from matplotlib and shouldn

Re: [sage-devel] sage and python 2.7: migration strategies?

2011-06-01 Thread Francois Bissey
> 2011/4/9 Francois Bissey : > > It turns out that warnings are not visible to the end users anymore. > > This is according to the python documentation: > > http://docs.python.org/library/warnings.html > > Section 27.6.5 to be precise. > > Actually more explicit in http://docs.python.org/using/cmdl

[sage-devel] Sphinx conf and online doc...

2011-06-01 Thread Florent Hivert
Hi there, I'm working on a few ticket to improve the handling of the doc: #11251 Add todo extension to Sphinx #9128 Sphinx should be aware of all.py to find its links #11263 Markup ".. link" is wrong in the developer guide. In order to do it I have to change Sphinx configuration in

[sage-devel] Re: Iterating over finite extension fields.

2011-06-01 Thread D. Monarres
Hello all, Don't mean to reply to my own question. I guess what I am wondering is why the finite extension of a finite field isn't a finite field. By having the results being a polynomial ring over the prime field it seems as if a lot is lost. Is there room to alter this behavior, or was there a c

Re: [sage-devel] sage and python 2.7: migration strategies?

2011-06-01 Thread Paulo César Pereira de Andrade
2011/4/9 Francois Bissey : > It turns out that warnings are not visible to the end users anymore. > This is according to the python documentation: > http://docs.python.org/library/warnings.html > Section 27.6.5 to be precise. > Actually more explicit in http://docs.python.org/using/cmdline.html : >

[sage-devel] 2D and 3D aspect ratio inconsistencies

2011-06-01 Thread Sébastien Labbé
Hi Sage-Devel, There are some inconsistencies with the behavior of aspect ratio when playing with 2D and 3D graphics. Here are examples that illustrate these. 2D : === sage: squareA = line([(0,0),(0,1),(1,1),(1,0),(0,0)]) sage: squareB = line([(3,7),(3,8),(4,8),(4,7),(3,7)]) sage: G = squareA +

[sage-devel] Re: 2D and 3D aspect ratio inconsistencies

2011-06-01 Thread slabbe
> Meanwhile, do you know a oneliner (simpler than the one above) that > draw 3d graphics object with aspect ratio 1, i.e. where cube looks > like cube? BTW, I know this works : sage: G = cube((10,5,3)) + cube((-7,-3,0)) sage: G.show(aspect_ratio=1) but the problem is that this returns None and

[sage-devel] Fwd: relaese of NZMATH version 1.1

2011-06-01 Thread John Cremona
FYI John -- Forwarded message -- From: NAKAMULA, Ken Date: Wed, Jun 1, 2011 at 3:13 PM Subject: relaese of NZMATH version 1.1 To: nmbrt...@listserv.nodak.edu Dear number theorists, We are pleased to announce the release of NZMATH 1.1. NZMATH is a Python based system for numb

Re: [sage-devel] Reduction type of elliptic curve versus reduction type of it's minimal model.

2011-06-01 Thread John Cremona
I think this thread should be on sage-nt so I am copying it there. I disagree that E.has_good_reduction(p) should work with the current, possibly non-minimal model. To make the output from your session more consistent would it not be better for E.reduction(p) to be more clever, and first replace

[sage-devel] Reduction type of elliptic curve versus reduction type of it's minimal model.

2011-06-01 Thread Maarten Derickx
Cause of the slight difference between an elliptic curve and it's minimal model we have the some inconsistent behavior in sage as shown at the end of this post. I think this behaviour is lightly confusing, and error prone. I think that in this case E.has_good_reduction(5) should return false becau

[sage-devel] Trac: change report {11} Tickets with positive review

2011-06-01 Thread Jeroen Demeyer
Can somebody who knows how Trac and SQL work please add a "dependencies" field to http://trac.sagemath.org/sage_trac/report/11 and remove the completely superfluous "status" field? Also, a "last modified" would be much more interesting than "created". -- To post to this group, send an email to s