Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

2017-02-25 Thread Francois Bissey
Oh I see, so you will go with clang all the way because that’s the default. I guess you know the score at https://trac.sagemath.org/ticket/12426 it compiles but doctests are failing left and right. But I haven’t had time to touch the thing in 3 months. Francois > On 26/02/2017, at 20:49, Isuru Fe

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

2017-02-25 Thread Isuru Fernando
Thanks. This is using conda's python, so will have to patch that as well. Regards, Isuru Fernando On Sun, Feb 26, 2017 at 1:09 PM, Francois Bissey < francois.bis...@canterbury.ac.nz> wrote: > That’s because python doesn’t do c++ compilation properly out of the box. > That’s https://bugs.python

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

2017-02-25 Thread Francois Bissey
That’s because python doesn’t do c++ compilation properly out of the box. That’s https://bugs.python.org/issue1222585 look it up. I will probably patch sage’s python in the near future - when I have time. François > On 26/02/2017, at 20:27, Isuru Fernando wrote: > > Anybody know why some python

Re: [sage-devel] State of sage built with clang/clang++ on OS X - update

2017-02-25 Thread Isuru Fernando
Anybody know why some python extensions with C++ as the language are compiled with -std=c99? I'm using sage-7.5.1 Log is below https://travis-ci.org/isuruf/staged-recipes/builds/205439821#L6669 Regards, Isuru Fernando On Tue, Oct 4, 2016 at 1:14 PM, Francois Bissey < francois.bis...@canterbury

[sage-devel] integration algorithms

2017-02-25 Thread Ralf Stephan
Users of integrate() usually don't care which "algorithm" is used, just that the thing is solved. At the moment the default behaviour is calling Maxima only, and you have to know/read that you can try other algorithms too. Many beginners don't know about this. I propose to make the default "try al

[sage-devel] Re: SageNB -> Jupyter conversion needs testers

2017-02-25 Thread kcrisman
> At https://trac.sagemath.org/ticket/22433 there is a ticket implementing > a move from SageNB towards Jupyter. It does conversion of SageNB > notebooks to Jupyter, hopefully with little loss of functionality (but I > know it's not 100% perfect and it never will be). If you are currently > u

Re: [sage-devel] fail to build mpir

2017-02-25 Thread 'Bill Hart' via sage-devel
The new MPIR fixes this and will be out by the 28th. On Thursday, 23 February 2017 21:02:21 UTC+1, vdelecroix wrote: > > Thanks! Applying the patch it just went fine. > > (I might create a relevant patch for Sage but we might migrate to the > newer mpir in preparation...) > > On 23/02/2017 20:3

[sage-devel] Re: fail to build openblas

2017-02-25 Thread Dima Pasechnik
a quicker option is to use system's Atlas. This is described in the installation manual, where various environment variables are discussed. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails f