[sage-devel] Sage-6.5 Source Fails to Compile

I'm trying to compile Sage-6.5 on 64-bit Linux (Gentoo using gcc-4.8.3) export MAKE="make -j16" make ssl > make.out 2>&1 & from the end of make: Successfully installed gf2x-1.1.p1 Deleting temporary build directory /dev/shm/sage-6.5/local/var/tmp/sage/build/gf2x-1.1.p1 F

Re: [sage-devel] Re: Addition of zero in the coercion model

Hi In my case "0 + MyElement" does find a common parent, namely the modular forms _ring_. So basically in my case "0 + some_element" is the same as "some_element.as_ring_element()", unless the weight of some_element (resp. its parent) is 0 with multiplier 1 in which case ZZ coerces into the spac

[sage-devel] Re: Addition of zero in the coercion model

Hi Eric, On 2015-02-21, Eric Gourgoulhon wrote: > It seems that a possible way to have 0 + MyElement work even if ZZ does= >=20 > not coerce to MyElement.parent() is to have=20 > MyElement.parent()._element_constructor_ accept 0 (i.e. Integer(0)) as an= >=20 > argument and return the zero element

Re: [sage-devel] Re: Addition of zero in the coercion model

Le samedi 21 février 2015 23:09:24 UTC+1, Jonas Jermann a écrit : > > Hi > > It's a good idea but it won't work (in fact the _element_constructor_ > does accept zero correctly in my case). The coercion framework _first_ > tries to find a common parent and _then_ the rest happens. > At least

[sage-devel] Re: how to unsubscribe from Trac ticket updates

http://trac.edgewall.org/ticket/9971 On Saturday, February 21, 2015 at 10:42:31 PM UTC+1, kcrisman wrote: > > Hi, I have been getting email updates for a ticket that I commented >>> on a long time ago and I was wondering if I can unsubscribe from the >>> updates. >> >> >> I know at least one wa

Re: [sage-devel] Re: Addition of zero in the coercion model

Hi It's a good idea but it won't work (in fact the _element_constructor_ does accept zero correctly in my case). The coercion framework _first_ tries to find a common parent and _then_ the rest happens. Best Jonas On 21.02.2015 22:59, Eric Gourgoulhon wrote: Hi, Le samedi 21 février 201

Re: [sage-devel] Re: Addition of zero in the coercion model

Hi, Le samedi 21 février 2015 21:59:05 UTC+1, Jonas Jermann a écrit : > > > The parent is a vector space / module not a ring. Every vector space > contains zero, so in my opinion from a conceptual point of view > adding zero should not change the parent space. > > However since it views 0 as an

[sage-devel] Re: how to unsubscribe from Trac ticket updates

> > Hi, I have been getting email updates for a ticket that I commented >> on a long time ago and I was wondering if I can unsubscribe from the >> updates. > > > I know at least one way: review the ticket! The author is usually > responsive > and quick with fixes. > > :) But more seriously,

[sage-devel] Re: Addition of zero in the coercion model

Hi Nils, On 2015-02-21, Nils Bruin wrote: > I'm not so sure. How does x+3 make unambiguous sense? If there is a coercion then (by definition of coercion in contrast to conversion) it is unique. > We can map ZZ onto > any cyclic subgroup. Yes, but at most one map is a coercion. > On the other

Re: [sage-devel] Re: 2x2 integer matrices

Hello Frederik, Finally, with some work the generic integer dense matrix class using flint (sage.matrix.matrix_integer_dense) is as fast as the 2x2 matrix. This is #17822. It is then not so hard to get rid of Matrix_integer_2x2. This is #17824. Vincent -- You received this message because you

Re: [sage-devel] Re: Addition of zero in the coercion model

Hi On 21.02.2015 22:13, Nils Bruin wrote: On Saturday, February 21, 2015 at 12:57:44 PM UTC-8, Simon King wrote: I.e., if P is a commutative additive group, then P.coerce_map_from(ZZ) should return a morphism in the category of commutative additive groups. Then, x+0 should work

[sage-devel] Re: Addition of zero in the coercion model

On Saturday, February 21, 2015 at 12:57:44 PM UTC-8, Simon King wrote: > > > I.e., if P is a commutative additive group, then P.coerce_map_from(ZZ) > should return a morphism in the category of commutative additive groups. > Then, x+0 should work (because the coercion map is a morphism in the >

[sage-devel] Re: Addition of zero in the coercion model

Hi Jonas, On 2015-02-21, Jonas Jermann wrote: > I'm confused. Why does the additive group of ZZ coerce into P? Oops, you are right. You can map ZZ onto an additive subgroup of P, but that would be not canonical and hence not a coercion. Anyway, Sage's coercion model works on the level of parent

Re: [sage-devel] Re: Addition of zero in the coercion model

Hi On 21.02.2015 21:57, Simon King wrote: On 2015-02-21, Simon King wrote: If ZZ does not coerce into the parent of your element, then the parent is not a (unitary) ring. PS: And if it is not a ring, then many things don't work as smoothly as they should. For example, if P is a commutative

Re: [sage-devel] Re: Addition of zero in the coercion model

Hi Simon On 21.02.2015 21:47, Simon King wrote: Hi Jonas, On 2015-02-21, Jonas Jermann wrote: ZZ does not coerce into myElement.parent() so I end up in a much larger space than myElement.parent(). However I would prefer if adding zero didn't change the parent space. If ZZ does not coerce in

[sage-devel] Re: Addition of zero in the coercion model

On 2015-02-21, Simon King wrote: > If ZZ does not coerce into the parent of your element, then the parent > is not a (unitary) ring. PS: And if it is not a ring, then many things don't work as smoothly as they should. For example, if P is a commutative additive group with an element x, then most

[sage-devel] Re: Addition of zero in the coercion model

Hi Jonas, On 2015-02-21, Jonas Jermann wrote: > ZZ does not coerce into myElement.parent() so I end up in a much > larger space than myElement.parent(). However I would prefer if adding > zero didn't change the parent space. If ZZ does not coerce into the parent of your element, then the parent

[sage-devel] Addition of zero in the coercion model

Hi When I do "0 + myElement" the coercion framework seems to map this to a common parent of 0 and myElement (by checking the parent of 0 and myElement). ZZ does not coerce into myElement.parent() so I end up in a much larger space than myElement.parent(). However I would prefer if adding zero di

Re: [sage-devel] sage-6.5.1?

I would appreciate any feedback on how well or not well the 14.04 trusty binary works on 14.10 utopic. Regards, Jan On 21 February 2015 at 14:54, Jan Groenewald wrote: > Hi > > I have now deleted the quantal/raring/saucy (they are all End of Life > already) on the PPA (to make space, the usual

Re: [sage-devel] Re: [debian] Strange numerical errors in sage's libpari code

On Feb 21, 2015 9:32 AM, "Volker Braun" wrote: > > Followups to sage-flame please... > I strongly agree. > > On Saturday, February 21, 2015 at 6:14:33 PM UTC+1, Felix Salfelder wrote: >> >> Hi Volker. >> >> actually i anticipate that you know better. anyway i reply. again. just >> for the record

Re: [sage-devel] Re: [debian] Strange numerical errors in sage's libpari code

Followups to sage-flame please... On Saturday, February 21, 2015 at 6:14:33 PM UTC+1, Felix Salfelder wrote: > > Hi Volker. > > actually i anticipate that you know better. anyway i reply. again. just > for the record. > > On Sat, Feb 21, 2015 at 06:55:26AM -0800, Volker Braun wrote: > > That

Re: [sage-devel] Re: [debian] Strange numerical errors in sage's libpari code

Hi Volker. actually i anticipate that you know better. anyway i reply. again. just for the record. On Sat, Feb 21, 2015 at 06:55:26AM -0800, Volker Braun wrote: > That is not true. What is true is that none of the core developers wants to > make their life even more difficult so that the debian

Re: [sage-devel] Re: [ARM] sage 6.5

The atlas build script just aborts with SAGE_ATLAS_ARCH=base, nothing else to see here. Pointing to a specific location for the atlas library isn't going to be much use in a binary that we distribute. On Saturday, February 21, 2015 at 4:54:12 PM UTC+1, Snark wrote: > > Le 21/02/2015 14:56, Vo

Re: [sage-devel] Re: [ARM] sage 6.5

Le 21/02/2015 14:56, Volker Braun a écrit : We have an ARM buildbot but it doesn't work: atlas install fails when SAGE_FAT_BINARY=yes is set. If you have an idea about suitable defaults then we could make it automatic *hint* Is there a trac ticket or some such on the matter, with some kind of

Re: [sage-devel] Re: [debian] Strange numerical errors in sage's libpari code

On Saturday, February 21, 2015 at 3:42:28 AM UTC+1, Michael Orlitzky wrote: > > On 02/20/2015 11:02 AM, kcrisman wrote: > > > >> > >> I no longer use sage for my day-to-day work, but when I was and I had > to > >> e.g. give a presentation, it was infuriating to find sage broken AGAIN > >> >

Re: [sage-devel] Re: [debian] Strange numerical errors in sage's libpari code

On Saturday, February 21, 2015 at 3:09:58 PM UTC+1, Felix Salfelder wrote: > > as it seems, hardly anybody (and about zero of the core developers) from > the sage community wants to make use of system-installed packages > (except for maybe gcc, ssl and whatnot). That is not true. What is true i

Re: [sage-devel] Re: [debian] Strange numerical errors in sage's libpari code

On Sat, Feb 21, 2015 at 03:58:29AM -0800, Volker Braun wrote: > [..] it still doesn't work. you keep saying that. but does it matter? the configuration worked pretty good as a proof-of-concept. i am sorry if your expectations were higher. note that this particular part was just optional within the

[sage-devel] Re: [ARM] sage 6.5

We have an ARM buildbot but it doesn't work: atlas install fails when SAGE_FAT_BINARY=yes is set. If you have an idea about suitable defaults then we could make it automatic *hint* On Saturday, February 21, 2015 at 2:30:10 PM UTC+1, Snark wrote: > > Hi, > > is there an ARM build box which will

[sage-devel] [ARM] sage 6.5

Hi, is there an ARM build box which will take care of preparing a bdist which I'll just have to unpack, or shall I build such a bdist as usual ? Snark on #sagemath -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group

Re: [sage-devel] Re: formatted latex-output / typeset in ipython notebook

Am 2015-02-21 um 12:51 schrieb Volker Braun: > This will work as a side-effect of http://trac.sagemath.org/ticket/17234 Excellent :) -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it,

Re: [sage-devel] sage-6.5.1?

Hi I have now deleted the quantal/raring/saucy (they are all End of Life already) on the PPA (to make space, the usual size of a PPA is 2G, mine has been increased and status is now 4.3 GiB (27.05%) of 16.0 GiB) after the changes below. I'm suprised those were not deleted automatically. I request

Re: [sage-devel] Re: [debian] Strange numerical errors in sage's libpari code

On Saturday, February 21, 2015 at 12:26:26 PM UTC+1, Snark wrote: > > Felix Salfelder did a GSOC about using a configure script. You keep saying that but it still doesn't work. Nor is it a particularly good way of exposing a lot of configuration options (at least one per package). -- You re

[sage-devel] Re: formatted latex-output / typeset in ipython notebook

This will work as a side-effect of http://trac.sagemath.org/ticket/17234 On Friday, February 20, 2015 at 5:23:46 PM UTC+1, Daniel Krenn wrote: > > Dear all, > > what is the status in Sage

Re: [sage-devel] Re: [debian] Strange numerical errors in sage's libpari code

Le 21/02/2015 11:15, Volker Braun a écrit : I agree that we should have some user configuration mechanism to customize how we build packages (including replacing sage packages with distro dependencies), but going about it by patching Sage or adding $DISTRO subdirectories everywhere are crap. Some

Re: [sage-devel] Re: [debian] Strange numerical errors in sage's libpari code

I agree that we should have some user configuration mechanism to customize how we build packages (including replacing sage packages with distro dependencies), but going about it by patching Sage or adding $DISTRO subdirectories everywhere are crap. Something like yaml config files (e.g. hashdis