[sage-devel] Re: Parent structure class hierarchy

I realized that this question is a bit unclear as it links to a URL with a lot of stuff on it, but all I had in mind was the part with heading The Abstract Element Class Hierarchy. This is just a list of all the pre-existing element classes which was very handy for figuring out what's there

[sage-devel] Re: Parent structure class hierarchy

Hi Simon, Thanks for your reply. I think I see the source of my confusion. Best, Joe On Saturday, August 6, 2016 at 4:31:37 PM UTC-4, Simon King wrote: > > Hi John, > > On 2016-08-06, Joseph Hundley wrote: > > I remark that maybe when someone qualified has some time

[sage-devel] Re: doc.sagemath.org gone from google

As I understand them canonical URLs distinguish between the same content accessed through different URL forms. Currently Google thinks the documentation is mostly located at www.sagemath.org/doc/ while we want it to appear at

Re: [sage-devel] Where should binary form reduction live?

Hi, Rebecca, On Aug 7, 2016, at 14:02 , Rebecca Miller wrote: > I am implementing Cremona and Stoll's Binary Form Reduction Algorithm. I'm > just not sure where it should live. I had some houghts but would like > opinions. Currently there is just a Quadratic Forms folder. I could create a >

[sage-devel] Where should binary form reduction live?

Hello All, I am implementing Cremona and Stoll's Binary Form Reduction Algorithm. I'm just not sure where it should live. I had some houghts but would like opinions. Currently there is just a Quadratic Forms folder. I could create a folder containing just this algorithm, or I could

[sage-devel] Re: How to share extern variables accross modules?

Jeroen Demeyer wrote: > On 2016-08-07 17:26, Simon King wrote: >>I build all these extension modules with >> libraries = ['mtx', 'modres'] > > This isn't the topic of this thread, but I think it is better style to > never put libraries in module_list.py. I prefer putting libraries in

Re: [sage-devel] Re: How to share extern variables accross modules?

On 2016-08-07 17:26, Simon King wrote: I build all these extension modules with libraries = ['mtx', 'modres'] This isn't the topic of this thread, but I think it is better style to never put libraries in module_list.py. I prefer putting libraries in "# distutils" directives where

[sage-devel] Re: How to share extern variables accross modules?

Volker Braun wrote: > On Sunday, August 7, 2016 at 5:26:56 PM UTC+2, Simon King wrote: > > - My cohomology code (Python/Cython) cimports from sage.libs.modres, > sage.libs.meataxe and sage.matrix.matrix_gfpn_dense. > I build all these extension modules with >libraries

[sage-devel] Re: doc.sagemath.org gone from google

Yes, you are right, this sounds like a really good idea! -- h On Sun, Aug 7, 2016 at 6:14 PM, Volker Braun wrote: > Presumably Google decided that combinat is the canonical url, right? > Hiding combinat is only kicking the problem down the road, there are > presumably

[sage-devel] Re: doc.sagemath.org gone from google

Presumably Google decided that combinat is the canonical url, right? Hiding combinat is only kicking the problem down the road, there are presumably many copies of the Sage docs hosted somewhere. The correct solution would be to include a http://doc.sagemath.org/path/to/help.html"/> in our docs

[sage-devel] Re: How to share extern variables accross modules?

On Sunday, August 7, 2016 at 5:26:56 PM UTC+2, Simon King wrote: > > - My cohomology code (Python/Cython) cimports from sage.libs.modres, > sage.libs.meataxe and sage.matrix.matrix_gfpn_dense. > I build all these extension modules with >libraries = ['mtx', 'modres'] > in

[sage-devel] Re: doc.sagemath.org gone from google

Btw, try http://www.bing.com/search?q=sage+Elements+of+Quotients+of+Univariate+Polynomial+Rings https://yandex.ru/search/?text=sage%20Elements%20of%20Quotients%20of%20Univariate%20Polynomial%20Rings

[sage-devel] Re: doc.sagemath.org gone from google

Does anyone know who is administrating the combinat pages? Hiding those pages could help. Besides that, I'm working with Paul Masson for months now to fix these indices. It's a stubborn problem, though... -- h On Sun, Aug 7, 2016 at 5:25 PM, William Stein wrote: > I'm

[sage-devel] Re: How to share extern variables accross modules?

Hi Volker, On 2016-08-07, Volker Braun wrote: > On Sunday, August 7, 2016 at 3:04:18 PM UTC+2, Simon King wrote: >> >> OK, then I'll open a ticket to let the meataxe package provide a shared >> library. My to-be-newstylified cohomology package relies on C library >> that

[sage-devel] doc.sagemath.org gone from google

I'm googling for links to the sage reference manual, e.g., https://www.google.com/search?q=sage+Elements+of+Quotients+of+Univariate+Polynomial+Rings=1C5CHFA_enUS691US691=sage+Elements+of+Quotients+of+Univariate+Polynomial+Rings=chrome..69i57j69i64.1153j0j7=chrome=UTF-8 and they now **all**

[sage-devel] Re: How to share extern variables accross modules?

Simon King wrote: > Hi Volker, > > On 2016-08-07, Volker Braun wrote: >> The relevant criterion is: No other module links with -lmtx > > OK, then I'll open a ticket to let the meataxe package provide a shared > library. My to-be-newstylified cohomology package relies on C

[sage-devel] Re: How to share extern variables accross modules?

On Sunday, August 7, 2016 at 3:04:18 PM UTC+2, Simon King wrote: > > OK, then I'll open a ticket to let the meataxe package provide a shared > library. My to-be-newstylified cohomology package relies on C library > that is created with -lmtx. That would work, but its probably a better design

[sage-devel] Re: How to share extern variables accross modules?

Hi Volker, On 2016-08-07, Volker Braun wrote: > The relevant criterion is: No other module links with -lmtx OK, then I'll open a ticket to let the meataxe package provide a shared library. My to-be-newstylified cohomology package relies on C library that is created with

[sage-devel] Re: trouble building 7.3 after 7.2 built ok

John Cremona wrote: > On 6 August 2016 at 19:16, leif wrote: >> John Cremona wrote: >>> None of the worked : sage -b and sage -ba all fail in the same way. >>> >>> Is this sort of warning normal: >> >> It's not actually a warning but usually rather an error, since this >>

[sage-devel] Re: How to share extern variables accross modules?

On Sunday, August 7, 2016 at 12:12:51 PM UTC+2, Simon King wrote: > > Now I am puzzled. By "link to the same extension module", you mean that > all my modules should do >from sage.libs.meataxe cimport * > and then all should be fine? But they do so and it is *not* fine! The relevant

[sage-devel] Re: How to share extern variables accross modules?

Simon King wrote: > Hey Leif, > > On 2016-08-07, leif wrote: >> Oh, didn't know and never noticed (TooManyPackages exception). >> >> (I thought you were still trying to get it in, which was problematic >> because some third-party program you also need still needed a quite

[sage-devel] Re: How to share extern variables accross modules?

Simon King wrote: > Hi Volker, > > On 2016-08-07, Volker Braun wrote: >> Is meataxe itself a shared or a static library? Or just C files that are >> compiled into the python module? You'll get one instance of MtxLibDir for >> each shared library that compiles the meataxe

[sage-devel] Re: How to share extern variables accross modules?

Simon King wrote: > Hey Leif, > > On 2016-08-07, leif wrote: >> Volker Braun wrote: >>> Is meataxe itself a shared or a static library? Or just C files that are >>> compiled into the python module? You'll get one instance of MtxLibDir >>> for each shared library that

[sage-devel] Re: How to share extern variables accross modules?

Hey Leif, On 2016-08-07, leif wrote: > Volker Braun wrote: >> Is meataxe itself a shared or a static library? Or just C files that are >> compiled into the python module? You'll get one instance of MtxLibDir >> for each shared library that compiles the meataxe C files (or

[sage-devel] Re: How to share extern variables accross modules?

Hey Leif, On 2016-08-07, leif wrote: > Oh, didn't know and never noticed (TooManyPackages exception). > > (I thought you were still trying to get it in, which was problematic > because some third-party program you also need still needed a quite > old/obsolete version.) The

[sage-devel] Re: How to share extern variables accross modules?

Volker Braun wrote: > Is meataxe itself a shared or a static library? Or just C files that are > compiled into the python module? You'll get one instance of MtxLibDir > for each shared library that compiles the meataxe C files (or includes > the machine code from a static library). In other words,

Re: [sage-devel] Re: trouble building 7.3 after 7.2 built ok

On 6 August 2016 at 19:16, leif wrote: > John Cremona wrote: >> None of the worked : sage -b and sage -ba all fail in the same way. >> >> Is this sort of warning normal: > > It's not actually a warning but usually rather an error, since this > happens (or may happen) when

[sage-devel] Re: How to share extern variables accross modules?

Simon King wrote: > Hi > > On 2016-08-07, leif wrote: >> Simon, do you have some preliminary branch on trac? > > Not yet. And until Wednesday I will not have the bandwidth to upload > anything. But note that sage.libs.meataxe and > sage.matrix.matrix_gfpn_dense is in Sage

[sage-devel] Re: How to share extern variables accross modules?

Hi Volker, On 2016-08-07, Volker Braun wrote: > Is meataxe itself a shared or a static library? Or just C files that are > compiled into the python module? You'll get one instance of MtxLibDir for > each shared library that compiles the meataxe C files (or includes the

[sage-devel] Re: Parent structure class hierarchy

Hi Joseph, For what it's forth, I may tell what is done in SageManifolds (metaticket #18528 ): SageManifolds involves many parent classes. All of them are implemented as direct subclasses of Parent. Their algebraic structures (group, free module,

[sage-devel] Re: How to share extern variables accross modules?

Is meataxe itself a shared or a static library? Or just C files that are compiled into the python module? You'll get one instance of MtxLibDir for each shared library that compiles the meataxe C files (or includes the machine code from a static library). In other words, meataxe itself must be

[sage-devel] Re: How to share extern variables accross modules?

Hi On 2016-08-07, leif wrote: > Simon, do you have some preliminary branch on trac? Not yet. And until Wednesday I will not have the bandwidth to upload anything. But note that sage.libs.meataxe and sage.matrix.matrix_gfpn_dense is in Sage already (and is used when you do

[sage-devel] Re: How to share extern variables accross modules?

Hi Volker, On 2016-08-06, Volker Braun wrote: > On the C level both is possible; The header can declare it e.g. static, > then every compilation unit gets its own copy. Or it can declare it extern, > then it will be shared across compilation units. As I wrote, it *is*

[sage-devel] Re: How to share extern variables accross modules?

Volker Braun wrote: > Thats really a C-level question, the different modules will see the same > value iff the address of MtxLibDir is the same. > > On the C level both is possible; The header can declare it e.g. static, > then every compilation unit gets its own copy. Or it can declare it >