[sage-devel] Sage 5.3 on Ubuntu 12.04.1 64bit tests failed

2012-09-25 Thread Jan Groenewald
Hi I saw all these errors compiling sage 5.3 from source with make testlong (even more with make testalllong, though they seemed to expect magma to be installed). model name: Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz http://users.aims.ac.za/~jan/sage-5.3-ubuntu12.04.1-amd64-testlong.log

[sage-devel] Re: Pari stack growning out of bounds

2012-09-25 Thread Rob Beezer
Thanks, Dima. On Tuesday, September 25, 2012 10:08:13 AM UTC-7, Dima Pasechnik wrote: > > So this is a bug... Maybe more like: my mistake. I had my print versions of the complex/real algebraic numbers mixed up. Here is the essence of how these (exact) eigenvalues are computed for rational

Re: [sage-devel] Re: Bunch of small changes to sage/gsl/interpolation.pyx

2012-09-25 Thread Robert Bradshaw
+1 to a copy. There could be another method, say points(), that returns an (immutable) tuple. Even more sophisticated, one could return a list with copy-on-write semantics. On Tue, Sep 25, 2012 at 3:38 PM, mhampton wrote: > > It seems safer to return a copy and not a reference. The documentation

[sage-devel] Re: Bunch of small changes to sage/gsl/interpolation.pyx

2012-09-25 Thread mhampton
It seems safer to return a copy and not a reference. The documentation does make it clear that it returns a reference, so it can't really be called a bug. My guess is that there isn't any code out there that exploits that though, so I would vote to not bother with a deprecation warning. -Ma

Re: [sage-devel] Opinion on "assert"

2012-09-25 Thread Nicolas M. Thiery
On Tue, Sep 25, 2012 at 03:18:48PM -0700, Volker Braun wrote: >So because its hard to write good error messages we are better off not >even trying? Obviously not :-) But there are a lot of places where there is no error checking whatsoever. So I want to encourage devs to write at least so

Re: [sage-devel] Safe-5.3 failed to be built on Mountain Lion (OS X 10.8)

2012-09-25 Thread JBT
John, FYI, here is the uname info: >$ uname -a Darwin jbtlap.ssl.berkeley.edu 12.2.0 Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64 x86_64 On Tuesday, September 25, 2012 3:16:35 PM UTC-7, John H Palmieri wrote: > > > > On Tuesday, September 25,

Re: [sage-devel] Re: Opinion on "assert"

2012-09-25 Thread Nicolas M. Thiery
On Mon, Sep 24, 2012 at 07:10:01AM -0500, Jason Grout wrote: > On 9/24/12 3:55 AM, Nicolas M. Thiery wrote: > >That being said, if there is a way to raise ValueError in a way that > >can be turned off like for assertions, I am happy to change my mind! > >(I am missing this from MuPAD; we could even

Re: [sage-devel] Opinion on "assert"

2012-09-25 Thread Volker Braun
On Tuesday, September 25, 2012 11:16:07 PM UTC+1, Nicolas M. ThiƩry wrote: > Precisely: if you do a grep, you can see that most of the error > messages are verbose and don't bring anymore information than a plain > assert. So because its hard to write good error messages we are better off not

Re: [sage-devel] Safe-5.3 failed to be built on Mountain Lion (OS X 10.8)

2012-09-25 Thread John H Palmieri
On Tuesday, September 25, 2012 3:11:52 PM UTC-7, JBT wrote: > > Michael, > > OK, I didn't try either of the two things last time. But I didn't get > lucky either after 'make clean' and deleting old scipy package. It failed > at the same spot. > > JBT > > On Tuesday, September 25, 2012 3:02:30 P

Re: [sage-devel] Opinion on "assert"

2012-09-25 Thread Nicolas M. Thiery
On Mon, Sep 24, 2012 at 02:13:30AM -0700, Volker Braun wrote: >On Monday, September 24, 2012 9:55:34 AM UTC+1, Nicolas M. ThiA(c)ry >wrote: > > - It's very concise, readable and to the point. Compare: > assert i > 0 >With: > if i <= 0: >

Re: [sage-devel] Safe-5.3 failed to be built on Mountain Lion (OS X 10.8)

2012-09-25 Thread JBT
Michael, OK, I didn't try either of the two things last time. But I didn't get lucky either after 'make clean' and deleting old scipy package. It failed at the same spot. JBT On Tuesday, September 25, 2012 3:02:30 PM UTC-7, yomcat wrote: > > On 26/09/2012, at 9:45 AM, JBT > wrote: > > Hi, Joh

Re: [sage-devel] Safe-5.3 failed to be built on Mountain Lion (OS X 10.8)

2012-09-25 Thread Michael Welsh
On 26/09/2012, at 9:45 AM, JBT wrote: > Hi, John, > > Thanks for the tip. I tried it, but no luck :-( The 'make' got stuck pretty > much at the same place. 1. Did you try again from scratch? Either by running 'make clean' or unpacking the source again. 2. Did you delete the older scipy spkg?

[sage-devel] Re: Safe-5.3 failed to be built on Mountain Lion (OS X 10.8)

2012-09-25 Thread JBT
Hi, John, Thanks for the tip. I tried it, but no luck :-( The 'make' got stuck pretty much at the same place. JBT On Tuesday, September 25, 2012 2:12:25 PM UTC-7, John H Palmieri wrote: > > > > On Tuesday, September 25, 2012 1:57:42 PM UTC-7, JBT wrote: >> >> Hi, >> >> I tried to build sage fr

[sage-devel] Re: Safe-5.3 failed to be built on Mountain Lion (OS X 10.8)

2012-09-25 Thread John H Palmieri
On Tuesday, September 25, 2012 1:57:42 PM UTC-7, JBT wrote: > > Hi, > > I tried to build sage from source code on my mac running Mountain lion > (10.8.2), but didn't succeed. > Sage won't build, as is, on Mountain Lion. Several of us have had good luck with the following procedure: - make s

[sage-devel] Safe-5.3 failed to be built on Mountain Lion (OS X 10.8)

2012-09-25 Thread JBT
Hi, I tried to build sage from source code on my mac running Mountain lion (10.8.2), but didn't succeed. I followed the instruction of the README on sage website, i.e., enter the source code folder and run 'make'. I pasted the last portion of the log from the terminal below. Also, in case it

Re: [sage-devel] Removing sage/structure/element_verify.py?

2012-09-25 Thread kcrisman
On Tuesday, September 25, 2012 3:59:59 PM UTC-4, David Roe wrote: > > I agree that this file should be removed. The verification that it's > doing should be performed by TestSuite now. We should ensure that all of > the conditions checked in this file are still checked when running the > Tes

Re: [sage-devel] Removing sage/structure/element_verify.py?

2012-09-25 Thread David Roe
I agree that this file should be removed. The verification that it's doing should be performed by TestSuite now. We should ensure that all of the conditions checked in this file are still checked when running the TestSuite on ring elements, module elements, etc. David On Tue, Sep 25, 2012 at 1:1

[sage-devel] Removing sage/structure/element_verify.py?

2012-09-25 Thread Jeroen Demeyer
I bumped by chance on the file sage/structure/element_verify.py This file: 1) is ophaned, i.e. nothing else in Sage depends on it 2) isn't mentioned in a single Trac ticket 3) hasn't seen any serious modifications since its creation in 2006 4) doesn't have any doctest So my guess is that it isn't

[sage-devel] Re: #matrix Class for load matrix from file

2012-09-25 Thread Jason Grout
On 9/25/12 12:15 PM, Raniere Gaia Silva wrote: Hi, I would like ask what you think about a class/interface for load matrix from file, e.g., Matlab, HB,//MPS, ... Great! You might look at the numpy loadtxt function, as well as the other numpy functions for loading matrices from files. Thanks

[sage-devel] #matrix Class for load matrix from file

2012-09-25 Thread Raniere Gaia Silva
Hi, I would like ask what you think about a class/interface for load matrix from file, e.g., Matlab, HB,* *MPS, ... Raniere -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsu

[sage-devel] Re: Pari stack growning out of bounds

2012-09-25 Thread Dima Pasechnik
On Wednesday, 26 September 2012 00:54:44 UTC+8, Rob Beezer wrote: > > To summarize some of this discussion more carefully: > > Eigenvalues of a symmetric rational matrix should already land in the > algebraic field (AA), so there is no need to convert them. Error messages > appear to come from

[sage-devel] Re: Pari stack growning out of bounds

2012-09-25 Thread Rob Beezer
To summarize some of this discussion more carefully: Eigenvalues of a symmetric rational matrix should already land in the algebraic field (AA), so there is no need to convert them. Error messages appear to come from QQbar, since much of the functionality of AA is contained in the same module

[sage-devel] Re: Bunch of small changes to sage/gsl/interpolation.pyx

2012-09-25 Thread kcrisman
> > > One thing that I noticed when working on this patch is that Spline.list > returns a reference to the spline interpolation points (this is actually > noted in the documentation), allowing one again to change the interpolation > points without forcing the spline to be recomputed. This issue

[sage-devel] Bunch of small changes to sage/gsl/interpolation.pyx

2012-09-25 Thread Joris Vankerschaver
Hi everybody, I made two small changes to the Sage interface for cubic spline interpolation (found in sage/gsl/interpolation.pyx). The first is at http://trac.sagemath.org/sage_trac/ticket/13519 and concerns a small bug which prevents splines from being recomputed when the interpolation po

[sage-devel] Re: Pari stack growning out of bounds

2012-09-25 Thread Dima Pasechnik
On Tuesday, 25 September 2012 15:31:09 UTC+8, Dima Pasechnik wrote: > > As suggested below, it might work if you replace the line > s = g.spectrum() > with > s = [AA(xx) for xx in g.spectrum()] > This still doesn't really work, but s = [RR(xx) for xx in g.spectrum()] does. You'd also need to

[sage-devel] Re: Pari stack growning out of bounds

2012-09-25 Thread Dima Pasechnik
As suggested below, it might work if you replace the line s = g.spectrum() with s = [AA(xx) for xx in g.spectrum()] making all the eigenvalues real (as they should be, as you generate undirected graphs) On Tuesday, 25 September 2012 04:18:03 UTC+8, Jernej Azarija wrote: > > Consider the followi

Re: [sage-devel] Pari stack growning out of bounds

2012-09-25 Thread Dima Pasechnik
On Tuesday, 25 September 2012 14:35:17 UTC+8, Jeroen Demeyer wrote: > > On 2012-09-24 22:29, John Cremona wrote: > > It seems computationally hard to test if an element of QQbar > > is positive > What does it even mean for an element of QQbar to be positive? > Indeed, in general this makes