Re: [sage-devel] wasm

On Tue, Apr 30, 2024 at 3:29 AM 'Doris Behrendt' via sage-devel < sage-devel@googlegroups.com> wrote: > Hi all, > > My team is about to develop a webapp where we want to factor polynomials > with coefficients in ZZ. > We want to offer a dropdown menu where the user can select the base ring > and t

Re: [sage-devel] Re: approve github actions

On Tue, May 14, 2024 at 9:13 PM Dima Pasechnik wrote: > > > On 14 May 2024 22:55:01 BST, "julian...@fsfe.org" > wrote: > >I granted "write" permissions to you. That seems to be the required > >permission to approve workflow runs. > > IIRC, such permissions are automatic for the members of triage

Re: [sage-devel] Proposal (redo): Make pytest, pytest_mock, pytest_xdist + dependencies standard packages

On Fri, May 31, 2024 at 12:38 PM Dima Pasechnik wrote: > On Thu, May 30, 2024 at 11:25 PM Matthias Koeppe > wrote: > > > > We added the packages as optional "pip" packages (see > https://deploy-livedoc--sagemath.netlify.app/html/en/developer/packaging#package-types > for the terminology), each m

Re: [sage-devel] Proposal (redo): Make pytest, pytest_mock, pytest_xdist + dependencies standard packages

On Wed, Jun 5, 2024 at 4:25 PM Matthias Koeppe wrote: > On Monday, June 3, 2024 at 12:29:14 PM UTC-7 dim...@gmail.com wrote: > > pytest can be kept a pip package, just promoted to standard. > > > It cannot, per existing policy. > > And the policy exists because it was made in awareness of the lim

Re: [sage-devel] Exception in Kquo.=Kyx.quotient([x^2+x+1]): Can only reduce polynomials over fields.

This seems to work, though I don't know exactly what you want to do with it. sage: K. = ZZ[] sage: n=13*random_prime(2**50) sage: f=x^2+x+1 sage: Kquo = K.quo(K.ideal(n,f)) sage: Kquo Quotient of Multivariate Polynomial Ring in x, y over Integer Ring by the ideal (10233078999195559, x^2 + x + 1) s

Re: [sage-devel] Italicizing inside a literal block

Could you explain more why you want to italicize something inside a literal block? David On Sat, Jun 22, 2024 at 10:39 PM Janmenjaya Panda < janmenjaya.panda...@gmail.com> wrote: > Could someone please mention, how to italicize a particular term inside a > literal block? > Use of `term` results a

Re: [sage-devel] Any tips for Maxima migrating to GitHub

The code that we used for the Trac to github migration is in this repository . Some things (including associating trac usernames with github usernames and creating issues, PRs and comments made by those users) required cooperation with Github and did not

Re: [sage-devel] Re: Policy discussion about hiding GitHub comments

We are starting this thread for two reasons. 1. Kwankyu asked for clarity on who can mark comments as off topic. 2. You marked this comment as off-topic, which asked for clarification on the action you had just taken removing th

Re: [sage-devel] Owners and Managers of sage-devel and other Google Groups: Please identify

On Thu, Aug 22, 2024 at 10:32 PM Matthias Koeppe wrote: > We are currently collecting the information which individuals manage the > project's infrastructure in > https://github.com/sagemath/sage/wiki/Infrastructure > > The information who is Owner or Manager of most of our project's Google > Gro

Re: [sage-devel] Re: Memory leak in |EllipticCurve([n,0]).root_number()| and problem in algebraic geometry

On Fri, Aug 30, 2024 at 8:02 AM Georgi Guninski wrote: > For a start, I have been killing sage bugs since 2012 [1]: > and have debugged some of them. > I think I deserve to be listed as sage contributor for wasting my time > and electricity. > We are always happy to acknowledge contributions.

Re: [sage-devel] Policy discussion about blocking others on Github

On Sat, Sep 7, 2024 at 7:11 AM 'Doris Behrendt' via sage-devel < sage-devel@googlegroups.com> wrote: > Dear list, > > boaaahhh come on guys! I again could't read all the past mails and cannot > comment objectively, but subjectively this feels like Kindergarten. Perhaps > Dima and Matthias (and the

[sage-devel] Discussion list for Sage governance

Dear Sage developers, One of the common themes that came out of the Community Survey this summer was some dissatisfaction with our governance model. Personally, I agree with much of the criticism: I think that relying on sage-d

[sage-devel] Re: Discussion list for Sage governance

Here's a functional link to join the group: https://groups.google.com/g/sage-government. Sorry for the broken link! David On Fri, Nov 29, 2024 at 2:09 PM David Roe wrote: > Dear Sage developers, > > One of the common themes that came out of the Community Survey > <https:/

Re: [sage-devel] Threading and cypari

rounds is welcome. David On Fri, Jun 4, 2021 at 3:54 PM David Roe wrote: > > > On Fri, Jun 4, 2021 at 3:24 PM Vincent Delecroix < > 20100.delecr...@gmail.com> wrote: > >> Thread support in cypari2 is definitely a reasonable requirement. >> I don't think t

Re: [sage-devel] Threading and cypari

a reasonable move is to revert the use of pointers on the > PARI stack. It created a lot of trouble with memory management. > > Best > Vincent > > On Thu, 14 Nov 2024 at 04:21, David Roe wrote: > > > > This bug is continuing to seriously impact the LMFDB. We have

Re: [sage-devel] Error after making some changes in the code

The first thing I would try would be to use `make build` rather than sage -br. The error you're seeing is related to missing flint, and sage -br only helps with changes to Cython code within the Sage library, not packages that Sage depends on. David On Sun, Feb 2, 2025 at 9:11 AM Pawani Agarwal <

Re: [sage-devel] Re: Example of an UFD in Sage for which is_unit is significantly slower than is_one

On Fri, Dec 13, 2024 at 2:38 PM 'Martin R' via sage-devel < sage-devel@googlegroups.com> wrote: > This does not look right, does it? > > sage: K. = NumberField(x^2-3) > sage: O = K.ring_of_integers() > sage: c = O(2*a + 4) > sage: isinstance(O, Field) > False > sage: isinstance(c, FieldElement) >

Re: [sage-devel] "There was a problem saving your comment. Please try again."

What is your github username? David On Tue, Dec 3, 2024 at 2:56 PM Jackson Walters wrote: > It seems I am not able to add comments to issues or PRs on GitHub. Is this > a GitHub issue or something specifically with Sage? > > -- > You received this message because you are subscribed to the Google

Re: [sage-devel] Re: using libgap in source

Yep, that should work. To find the right import statements, you can do sage: import_statements(libgap) from sage.libs.gap.libgap import libgap David On Thu, Dec 5, 2024 at 5:37 PM Jackson Walters wrote: > Perhaps I can just use > > from sage.libs.gap.libgap import libgap > > On Thursday, Decemb

Re: [sage-devel] Admin request: new sagemath-giac repository

Hi Michael, I've created sage-giac and added you as an admin. Let me know if you need anything else. Thanks for working on this! David On Thu, Feb 13, 2025 at 12:39 PM Michael Orlitzky wrote: > Hi, this is a friendly reminder that I am trying to move the

Re: [sage-devel] Urgent - wiki.sagemath is down

It seems to be up again. Thanks to whoever worked on this! David On Sun, Mar 16, 2025 at 11:39 PM David Roe wrote: > Looking at the index of Sage's infrastructure > <https://github.com/sagemath/sage/wiki/Infrastructure>, wiki.sagemath.org > seems to be maintained by Thier

Re: [sage-devel] Urgent - wiki.sagemath is down

Looking at the index of Sage's infrastructure , wiki.sagemath.org seems to be maintained by Thierry Monteil, who I've CCed. Hopefully this can be resolved once the workweek in France starts! David On Sun, Mar 16, 2025 at 9:38 PM Travis Scrimsh

<    5   6   7   8   9   10