Re: [sage-devel] Re: Can Sage compute the Groebner basis of a module?

On Tue, Oct 22, 2019 at 9:51 PM 'Bill Hart' via sage-devel wrote: > > > > On Friday, 18 October 2019 15:21:05 UTC+2, Dima Pasechnik wrote: >> >> Hi, >> well, Sage's functionality for modules over polynomial rings is quite >> limited. >> It assumes that a submodule of a free module is free. > > >

Re: [sage-devel] Re: Can Sage compute the Groebner basis of a module?

>From the Singular documentation [1]: "Hence any finitely generated [image: $R$]-module can be represented in S INGULAR by its module of relations." [1] https://www.singular.uni-kl.de/Manual/4-0-3/sing_134.htm On Tuesday, 22 October 2019 22:51:45 UTC+2, Bill Hart wrote: > > > > On Friday, 18

Re: [sage-devel] Re: Can Sage compute the Groebner basis of a module?

On Friday, 18 October 2019 15:21:05 UTC+2, Dima Pasechnik wrote: > > Hi, > well, Sage's functionality for modules over polynomial rings is quite > limited. > It assumes that a submodule of a free module is free. > In what way does it assume this? There are limitations, but I'm not so sure

Re: [sage-devel] Question about deprecation warnings: when do they appear in doctests vs. real life?

On Sunday, October 20, 2019 at 2:00:49 PM UTC-7, Nils Bruin wrote: > > [I think that behaviour is a bug in Python's warning machinery. It's a > silent failure to issue a warning in a case where some warning is almost > certainly desired]. > Correcting myself on this one. Nothing is wrong in

[sage-devel] Re: sage and emacs (and unicode)

Thank you! I didn't realise that a font might not be properly monospace! ("Noto Mono Regular" is beautiful, but doesn't work - "monospace regular" seems to work correctly, although it is not as nice to my eyes :-) -- You received this message because you are subscribed to the Google Groups

[sage-devel] Gram-Schmidt Procedure for Symbolic Ring

Hello everyone, I have a question regarding the implemented Gram-Schmidt procedure. Using a matrix in the symbolic ring leads to the following error message: m = matrix(SR, [[x,2*x],[x^2,1]]) m.gram_schmidt() ---

[sage-devel] Re: sage and emacs (and unicode)

Did you try to change the font in emacs until finding a correct font with constant width ? Le mardi 22 octobre 2019 12:22:43 UTC+2, Martin R a écrit : > > This is, superficially, a support question for a minor problem with emacs > and sage-shell-mode (and therefore possibly off topic, please

Re: [sage-devel] Compile sage with `-march=native` as a default

On 10/22/19 7:41 AM, Dima Pasechnik wrote: >> >> Set CFLAGS="-march=native" in your shell before running "make", and then >> pray that the sage packages respect that variable. > > many packages would ignore it, and C++ and Fortran modules won't be > affected by this, either. Well there's also

Re: [sage-devel] Compile sage with `-march=native` as a default

On Tue, Oct 22, 2019 at 12:34 PM Michael Orlitzky wrote: > > On 10/22/19 7:00 AM, 'Jonathan Kliem' via sage-devel wrote: > > I was wondering, if it was possible to compile sage (or parts of it) > > with `-march=native` or something similar (unless SAGE_FAT_BINARIES is set). > > Some time ago I

Re: [sage-devel] Compile sage with `-march=native` as a default

On 10/22/19 7:00 AM, 'Jonathan Kliem' via sage-devel wrote: > I was wondering, if it was possible to compile sage (or parts of it) > with `-march=native` or something similar (unless SAGE_FAT_BINARIES is set). > Some time ago I created #27122 > for this.

[sage-devel] Compile sage with `-march=native` as a default

I was wondering, if it was possible to compile sage (or parts of it) with `-march=native` or something similar (unless SAGE_FAT_BINARIES is set). Some time ago I created #27122 for this. Why do I care about it? (I was told that many parts of sage could

[sage-devel] sage and emacs (and unicode)

This is, superficially, a support question for a minor problem with emacs and sage-shell-mode (and therefore possibly off topic, please excuse). However, in truth the problem is slightly deeper. The superficial problem at hand is that unicode_art produces garbled output on my emacs (I am