Re: [sage-devel] Re: g95 - can we simply forget it exists?

2010-09-11 Thread Ondrej Certik
On Sat, Sep 11, 2010 at 6:29 PM, kcrisman wrote: > >> Is there any reason whatsoever to have g95 code in ATLAS, given we don't >> build >> ATLAS on OS X? > > No opinion - this sounds fine, but is beyond my knowledge. > >> > One more question about Mac --- how do you install gcc in there? Using >>

[sage-devel] Re: g95 - can we simply forget it exists?

2010-09-11 Thread kcrisman
> Is there any reason whatsoever to have g95 code in ATLAS, given we don't build > ATLAS on OS X? No opinion - this sounds fine, but is beyond my knowledge. > > One more question about Mac --- how do you install gcc in there? Using > > xcode? So I would just ship gfortran binary that is compatib

Re: [sage-devel] g95 - can we simply forget it exists?

2010-09-11 Thread François Bissey
> On 09/12/10 12:10 AM, François Bissey wrote: > > +1 to move to FC. > > I raised this back in November 2009 - William is against using FC. > > http://www.mail-archive.com/sage-devel@googlegroups.com/msg31854.html > I read the thread in question. I think more recent autotools don't check fortra

Re: [sage-devel] g95 - can we simply forget it exists?

2010-09-11 Thread Ondrej Certik
On Sat, Sep 11, 2010 at 5:56 PM, Dr. David Kirkby wrote: > On 09/12/10 12:10 AM, François Bissey wrote: > >> +1 to move to FC. > > I raised this back in November 2009 - William is against using FC. > > http://www.mail-archive.com/sage-devel@googlegroups.com/msg31854.html I read this, I think that

Re: [sage-devel] g95 - can we simply forget it exists?

2010-09-11 Thread Ondrej Certik
On Sat, Sep 11, 2010 at 5:42 PM, Ondrej Certik wrote: > On Sat, Sep 11, 2010 at 5:35 PM, Dr. David Kirkby > wrote: >> On 09/12/10 12:10 AM, François Bissey wrote: On 11 September 2010 21:48, Ondrej Certik  wrote: > > When building femhub and packages for femhub, I have to deal w

Re: [sage-devel] g95 - can we simply forget it exists?

2010-09-11 Thread Dr. David Kirkby
On 09/12/10 12:10 AM, François Bissey wrote: +1 to move to FC. I raised this back in November 2009 - William is against using FC. http://www.mail-archive.com/sage-devel@googlegroups.com/msg31854.html Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe

Re: [sage-devel] g95 - can we simply forget it exists?

2010-09-11 Thread Ondrej Certik
On Sat, Sep 11, 2010 at 5:35 PM, Dr. David Kirkby wrote: > On 09/12/10 12:10 AM, François Bissey wrote: >>> >>> On 11 September 2010 21:48, Ondrej Certik  wrote: When building femhub and packages for femhub, I have to deal with these fortran issues as well. And I never understood >>

Re: [sage-devel] Re: g95 - can we simply forget it exists?

2010-09-11 Thread Dr. David Kirkby
On 09/12/10 01:07 AM, kcrisman wrote: a) why sage used g95 in the first place (yes I know it's smaller, but it's not standard at all imho) Agreed. I can't see the point of it. Apparently because there was no gfortran for certain platforms. Now we assume Linuces (?) have this, but as Dima d

Re: [sage-devel] g95 - can we simply forget it exists?

2010-09-11 Thread Dr. David Kirkby
On 09/12/10 12:10 AM, François Bissey wrote: On 11 September 2010 21:48, Ondrej Certik wrote: When building femhub and packages for femhub, I have to deal with these fortran issues as well. And I never understood a) why sage used g95 in the first place (yes I know it's smaller, but it's not st

[sage-devel] Re: g95 - can we simply forget it exists?

2010-09-11 Thread kcrisman
> > a) why sage used g95 in the first place (yes I know it's smaller, but > > it's not standard at all imho) > > Agreed. I can't see the point of it. > Apparently because there was no gfortran for certain platforms. Now we assume Linuces (?) have this, but as Dima demonstrates, with OS X 10.4, so

Re: [sage-devel] g95 - can we simply forget it exists?

2010-09-11 Thread François Bissey
> On 11 September 2010 21:48, Ondrej Certik wrote: > > When building femhub and packages for femhub, I have to deal with > > these fortran issues as well. And I never understood > > > > a) why sage used g95 in the first place (yes I know it's smaller, but > > it's not standard at all imho) > > A

Re: [sage-devel] g95 - can we simply forget it exists?

2010-09-11 Thread David Kirkby
On 11 September 2010 21:48, Ondrej Certik wrote: > When building femhub and packages for femhub, I have to deal with > these fortran issues as well. And I never understood > > a) why sage used g95 in the first place (yes I know it's smaller, but > it's not standard at all imho) Agreed. I can't s

[sage-devel] Re: [sage-flame] Re: Sage is embarrassingly slow

2010-09-11 Thread Bill Hart
Just to be clear, I'm specifically talking about arithmetic by the way. Anything for which the python overhead is completely irrelevant, should of course be implemented in python. Arithmetic really screws up almost every aspect of computing. There's a group of related "full employment" problems wh

Re: [sage-devel] g95 - can we simply forget it exists?

2010-09-11 Thread Ondrej Certik
Hi Dave, On Thu, Sep 9, 2010 at 2:09 AM, Dr. David Kirkby wrote: > There's odd bits code scattered around in Sage that do tests for g95, which > is an old Fortran 95 compiler that in any modern Linux or Unix systems. > > According to Wikipedia > > http://en.wikipedia.org/wiki/G95 > > gfortran was

[sage-devel] Re: Sage is embarrassingly slow

2010-09-11 Thread Bill Hart
For really fast generics I think you may need some kind of jit. Are generics handled by cython code or python code in sage? Does it cache anything? I recently encountered similar problems anyhow. A generic rref took 20 minutes to reduce a tiny (by my standards) matrix as part of a factoring algor

[sage-devel] Re: OSX Clickable App

2010-09-11 Thread Jason Grout
On 9/11/10 1:27 PM, Ivan Andrus wrote: Sorry, I thought I had sent this earlier. On Sep 11, 2010, at 7:20 AM, Dan Drake wrote: On Tue, 31 Aug 2010 at 10:13AM -0700, kcrisman wrote: It is. I've also been testing this - you should try out the very latest version: http://boxen.math.washington.ed

[sage-devel] Re: g95 - can we simply forget it exists?

2010-09-11 Thread Dima Pasechnik
I got stuck at scipy: In the log below, the line beginning with "sage_fortran -Wall -shared -Wall -shared -undefined dynamic_lookup - bundle..." definitely looks weird, as -shared option should not be there... (I must also say that the error message looks weird, too, as there is no option -dynamic

Re: [sage-devel] Re: OSX Clickable App

2010-09-11 Thread Ivan Andrus
Sorry, I thought I had sent this earlier. On Sep 11, 2010, at 7:20 AM, Dan Drake wrote: > On Tue, 31 Aug 2010 at 10:13AM -0700, kcrisman wrote: >> It is. I've also been testing this - you should try out the very >> latest version: >> http://boxen.math.washington.edu/home/iandrus/ >> There are sti

[sage-devel] deprecation "since ..."

2010-09-11 Thread Jason Grout
Right now, the deprecation function (for giving deprecation warnings) has an option to say when the deprecation took effect. Because of the way release numbers are decided, and because patches can be delayed getting in, saying when a deprecation took place is very hard, if not practically im

Re: [sage-devel] Re: consistent style for sagemath.org and sage documentation

2010-09-11 Thread Minh Nguyen
Hi Rob, On Thu, Sep 2, 2010 at 8:17 AM, Rob Beezer wrote: > The > sick green has always been a bit jarring to my eye.  Maybe a light > beige or cream?  But not puce. Done. Please see the latest patch to ticket #9850 [1]. A preview [2] of what's to come is also attached with that ticket. [1] htt

[sage-devel] Re: How to deal with GAP's machine dependent random generator?

2010-09-11 Thread Dima Pasechnik
On Sep 11, 2:36 pm, Mike Hansen wrote: > On Fri, Sep 10, 2010 at 10:17 PM, Dima Pasechnik wrote: > > Does current_randstate().set_seed_gap() actually sets GAP's random > > seed, so that > > subsequent GAP commands make use of the correctly set seed? > > Yep. I see. Well, I am told that my GAP