[sage-devel] Re: Allowing correct upstream acknowledgement by default ?

The attribution mechanism works by running the session in a profiler in order to trace the execution. Since profiling incurrs a significant runtime overhead it must be off by default. On Friday, July 6, 2018 at 9:28:10 AM UTC+2, Simon King wrote: > > Hi Thierry, > > could it be that you

[sage-devel] Re: Method Resolution Order

On Friday, July 6, 2018 at 9:40:16 AM UTC-7, Friedrich Wiemer wrote: > > So why is the _repr_() method from the matrix class called and not from > LinearLayerGeneric? > > It is not. The special python method is __repr__. In various places in sage, __repr__ delegates to _repr_, but that is a

Re: [sage-devel] Re: adding cython/C code in top level of sagelib

On Friday, July 6, 2018 at 4:15:55 PM UTC+2, Jeroen Demeyer wrote: > > On 2018-07-06 16:08, John H Palmieri wrote: > > It’s already documented in the developer’s guide: > http://doc.sagemath.org/html/en/developer/coding_in_cython.html?highlight=module_list > > > > >John > > > > But

[sage-devel] Re: adding cython/C code in top level of sagelib

On Friday, July 6, 2018 at 4:08:46 PM UTC+2, John H Palmieri wrote: > > It’s already documented in the developer’s guide: > http://doc.sagemath.org/html/en/developer/coding_in_cython.html?highlight=module_list > > > the bottom line is that it's possible to miss this, especially as the section

[sage-devel] Re: Compiling Sage stops at PPL

your log says: checking for the GMP library version 4.1.3 or above... no configure: error: Cannot find GMP version 4.1.3 or higher. Did you run ./configure before running make? So this indicated that something got broken earlier. Check that there were no errors while installing MPIR package

[sage-devel] Method Resolution Order

With this code (follow up of https://groups.google.com/forum/#!topic/sage-devel/4uxI1XVtoDs): from sage.matrix.matrix_mod2_dense import Matrix_mod2_dense from sage.matrix.matrix_gf2e_dense import Matrix_gf2e_dense class LinearLayerGeneric: def _repr_(self): return "LinearLayer of

Re: [sage-devel] Representation of LinearLayers in the crypto module

Well, this seems to be due to another part of the file, I got a MWE to work, so I guess I will figure it out. -- 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, send an email to

Re: [sage-devel] Re: adding cython/C code in top level of sagelib

On 2018-07-06 16:08, John H Palmieri wrote: It’s already documented in the developer’s guide: http://doc.sagemath.org/html/en/developer/coding_in_cython.html?highlight=module_list John But don't use "libraries=", it's better to use "# distutils" directives at the top of your Cython

[sage-devel] Re: adding cython/C code in top level of sagelib

It’s already documented in the developer’s guide: http://doc.sagemath.org/html/en/developer/coding_in_cython.html?highlight=module_list John -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving

Re: [sage-devel] Representation of LinearLayers in the crypto module

Ah, this looks good! Interestingly, while this works in the sage notebook, changing it in the module results in an sage: from sage.crypto.linearlayer import LinearLayerFactory sage: LinearLayerFactory(GF(2))(MatrixSpace(GF(2), 2, 2), [1,0,0,1])

Re: [sage-devel] SageMath devel branch fails to build on Linux Mint 19; ntl, setuptools, ecl and givaro build failure

Regardless it's clear from the screenshot that this is just https://trac.sagemath.org/ticket/25731 On Fri, Jul 6, 2018, 13:55 BJH2017 wrote: > Sorry, here be the logs, didn't realize I could attach them. > > On Friday, 6 July 2018 21:49:35 UTC+10, Jeroen Demeyer wrote: >> >> On 2018-07-06

Re: [sage-devel] Representation of LinearLayers in the crypto module

Hi Friedrich, I was thinking maybe something like this: from sage.matrix.matrix_mod2_dense import Matrix_mod2_dense, from sage.matrix.matrix_gf2e_dense import Matrix_gf2e_dense class LinearLayer: def foo(self): return self[0, 1] def LinearLayerFactory(K): if K.characteristic()

Re: [sage-devel] SageMath devel branch fails to build on Linux Mint 19; ntl, setuptools, ecl and givaro build failure

On 2018-07-06 13:43, BJH2017 wrote: Have you tried clicking "Raw"? it should show you the full log.

Re: [sage-devel] SageMath devel branch fails to build on Linux Mint 19; ntl, setuptools, ecl and givaro build failure

Have you tried clicking "Raw"? it should show you the full log. On Friday, 6 July 2018 21:34:28 UTC+10,

Re: [sage-devel] SageMath devel branch fails to build on Linux Mint 19; ntl, setuptools, ecl and givaro build failure

On 2018-07-06 01:33, BJH2017 wrote: The logs for these dependencies are in this gist: https://gist.github.com/fusion809/cd1b666ce7530bfa376f2397ca5a498a. They seem to be truncated, hence useless. -- You received this message because you are subscribed to the Google Groups "sage-devel" group.

[sage-devel] Re: Representation of LinearLayers in the crypto module

Am Freitag, 6. Juli 2018 12:57:39 UTC+2 schrieb Friedrich Wiemer: > LinearLayer(test_m.parent(), test_m) > test1._m.__class__.__mro__ > this should of course be test1 = LinearLayer(test_m.parent(), test_m) test1._m.__class__.__mro__ -- You received this message because you are subscribed to

[sage-devel] Representation of LinearLayers in the crypto module

Hi, I worked on an implementation of linear layers (basically a matrix over GF(2) or GF(2^n) with some special methods) in the crypto module during the sage days 94 and came up with this: #25735. Martin commented that it might make sense to just inherit from an appropriate matrix class, to

[sage-devel] Re: Allowing correct upstream acknowledgement by default ?

Hi Thierry, could it be that you misunderstood the purpose of SAGE_PROFILE? It is not about "citing" upstream in the sense of "giving proper credit to when writing a paper". According to the installation manual: "SAGE_PROFILE - controls profiling support. If this is set to yes, profiling