Re: [sage-devel] coercion issue

2015-02-06 Thread Robert Bradshaw
Interesting. It seems the problem is that cm.discover_action(GF(5), ZZ, operator.div) tries to look for a right action on of cm.discover_action(GF(5), Frac(ZZ), operator.mul) which doesn't exist as there are no coercions between GF(5) and QQ. I posted a patch to http://trac.sagemath.or

[sage-devel] Re: flint-2.4.4 compile error for Sage-6.4 on MacOSX Mavericks

2015-02-06 Thread Bill Hart
Thanks. Unfortunately, I haven't been able to figure out what is causing this. It looks like your gmp.h is turning either mpn_com or mpn_com_n into __gmpn_com_n as it should. It certainly doesn't turn it into ___gmpn_com. I have absolutely no idea what could be causing the extra underscore, or

[sage-devel] Re: weil restriction for affine schemes as a functor?

2015-02-06 Thread Ben Hutz
This is now #17729 On Monday, February 2, 2015 at 8:59:33 PM UTC-5, Ben Hutz wrote: > > I'm interested in implementing Weil restriction (restriction of scalars) > for affine schemes. I see from #5569, that there is an implementation for > ideals. I'd like to extend this to affine schemes/points/

[sage-devel] Pari, SR, number fields, strings, and coercions

2015-02-06 Thread Marc Mezzarobba
Hi, The following example from q_analogues.py happens to work for a number of questionable reasons: sage: q_binomial(6,1,I) 1 + I I'm working on a patch that breaks (or fixes, depending how you look at it) one of the behaviors it relies on, and I'd like advice on how to handle the situati

Re: [sage-devel] Is CMake OK for a standard spkg?

2015-02-06 Thread Thierry Dumont
Le 06/02/2015 08:15, Francois Bissey a écrit : > Cmake is a reverse approach compared to autotools. You need cmake installed > to configure the software. The system to build (make or something else) is > somewhat OS dependent. autotool generate a script and you don’t need > auto tool installed on

Re: [sage-devel] Is CMake OK for a standard spkg?

2015-02-06 Thread Jeroen Demeyer
On 2015-02-06 14:42, Thierry Dumont wrote: But the autotools, too, are supposed to be installed system wide. Not true. Building a package using autotools doesn't require autotools. Autotools generates files like configure which are shipped with the sources. Executing those files does not requ

Re: [sage-devel] Is CMake OK for a standard spkg?

2015-02-06 Thread Francesco Biscani
On 6 February 2015 at 14:47, Jeroen Demeyer wrote: > > Not true. Building a package using autotools doesn't require autotools. > Autotools generates files like configure which are shipped with the > sources. Executing those files does not require autotools. But it requires some sort of GNU envir

[sage-devel] Re: Is CMake OK for a standard spkg?

2015-02-06 Thread Dima Pasechnik
On 2015-02-06, Thierry Dumont wrote: > Le 06/02/2015 08:15, Francois Bissey a écrit : >> Cmake is a reverse approach compared to autotools. You need cmake installed >> to configure the software. The system to build (make or something else) is >> somewhat OS dependent. autotool generate a script a

Re: [sage-devel] Is CMake OK for a standard spkg?

2015-02-06 Thread Francois Bissey
> On 7/02/2015, at 06:10, Dima Pasechnik wrote: > > On 2015-02-06, Thierry Dumont wrote: >> Le 06/02/2015 08:15, Francois Bissey a écrit : >>> Cmake is a reverse approach compared to autotools. You need cmake installed >>> to configure the software. The system to build (make or something else)

Re: [sage-devel] Sagemath : wild experiments

2015-02-06 Thread Julien Puydt
Hi, Le 05/02/2015 22:10, Julien Puydt a écrit : Good news ! I did some cleaning, and I now have all your symptoms ! Well, perhaps that's not that good a piece of news, but at least now I have something to play with. Ok, I found the time to fight with it some today. I followed those steps : -

[sage-devel] Re: flint-2.4.4 compile error for Sage-6.4 on MacOSX Mavericks

2015-02-06 Thread Xander Faber
Hi Bill, Thanks for the detailed instructions. mpir-2.7.0 and mpfr-3.1.2 build fine on my system. When I run the makefile for flint, I get the following messages after a while: ` CC ../build/fq_zech_poly_factor/fq_zech_poly_factor_print.o CC ../build/fq_zech_poly_factor/fq_zech_poly

[sage-devel] git upgrade?

2015-02-06 Thread kcrisman
>From the Github team, this mention: Don't forget: an important Git security vulnerability was fixed last December. If you haven't upgraded your Git client since then, we recommend that you do so as soon as possible. The new release, 2.3.0, includes the security fix, as do the maintenance relea

Re: [sage-devel] git upgrade?

2015-02-06 Thread Francois Bissey
On 7/02/2015, at 17:09, kcrisman wrote: > > From the Github team, this mention: > > Don't forget: an important Git security vulnerability was fixed last > December. If you haven't upgraded your Git client since then, we recommend > that you do so as soon as possible. The new release, 2.3.0, in