Re: [sage-devel] Error while installing SAGE

On Wed, Nov 18, 2020 at 2:39 AM Emmanuel Charpentier < emanuel.charpent...@gmail.com> wrote: > Ahem... > > Le mardi 17 novembre 2020 à 19:11:10 UTC+1, David Roe a écrit : > >> It looks like you ran out of disk space. I would suggest making more >> room on your har

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!]

For Zulip, zulipchat.com provides free hosting for open source projects. I'm fairly confident that we could export our history and import it to a new organization there fairly easily, if there's a consensus to do so. David On Thu, Dec 10, 2020 at 5:41 AM Dima Pasechnik wrote: > Dear all, > > I'm

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!]

On Thu, Dec 10, 2020 at 6:06 AM Dima Pasechnik wrote: > On Thu, Dec 10, 2020 at 10:49 AM David Roe wrote: > > > > For Zulip, zulipchat.com provides free hosting for open source > projects. I'm fairly confident that we could export our history and import > it to a new

Re: [sage-devel] Re: is ZZ(None) == 0 intentional?

It's certainly intentional: see line 662 of sage/rings/integer.pyx. Whether it's a good idea is another question. The motivation is as Travis said, that None behaves like False. But Python ints don't behave this way, in either Python 2 or Python 3. I'd be fine with a change so that ZZ(None) rais

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!]

On Thu, Dec 10, 2020 at 10:19 PM Samuel Lelievre wrote: > 2020-12-10 11:37:41 UTC, David Roe: > > > > On Thu, Dec 10, 2020 at 6:06 AM Dima Pasechnik: > > > > > > On Thu, Dec 10, 2020 at 10:49 AM David Roe: > > > > > > > > For Zulip, zulip

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!]

On Thu, Jan 7, 2021 at 3:30 PM Harald Schilly wrote: > On Thu, Jan 7, 2021 at 9:23 PM Dima Pasechnik wrote: > > Harald - can you take care of this? > > > > Uhm, what's happening? Could someone please summarize this for me? > zulip.sagemath.org used to point to a google virtual machine. We'd li

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!]

On Thu, Jan 7, 2021 at 3:49 PM Isuru Fernando wrote: > It should be sagemath.zulipchat.com right? (Instead of .org) > Yes, sorry for the typo! David > Isuru > > On Thu, Jan 7, 2021 at 2:47 PM David Roe wrote: > >> >> >> On Thu, Jan 7, 2021 at 3:30 PM Haral

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!]

There was an oversight in upgrading us to a sponsored account as an open source organization. They've done so now; let me know if you observe any similar issues going forward. David On Mon, Jan 18, 2021 at 12:33 PM Dima Pasechnik wrote: > On Mon, Jan 18, 2021 at 3:52 PM Samuel Lelièvre > wrote

Re: [sage-devel] Why does sage use different URLs for push and fetch?

On Sat, Jan 16, 2021 at 7:09 AM Dima Pasechnik wrote: > On Fri, Jan 15, 2021 at 10:33 PM Siddharth Bhat > wrote: > > > > In "git the hard way", it asks us to setup: > > > > [user@localhost sage]$ git remote add trac git:// > trac.sagemath.org/sage.git -t master > > [user@localhost sage]$ git rem

Re: [sage-devel] Attribute error when using [0..n] in a function

Are you writing this function in a .sage file or a .py file? The latter won't work, since it doesn't preparse the input. David On Wed, Apr 28, 2021 at 12:13 AM 'Justin C. Walker' via sage-devel < sage-devel@googlegroups.com> wrote: > A few details would help: > - what version of sage? > - what O

Re: [sage-devel] Proposal: Very short release cycle for Sage 9.4

There are also a couple of standard package upgrades to FLINT and arb. David On Mon, May 10, 2021 at 7:44 PM Dima P

Re: [sage-devel] Re: Minimum Python version to 3.8

One way to do it is to modify the auto_optional_tags variable in sage.doctest.control lines 47-54 to add a more specific python version tag. This doesn't get you inequalities in versions though. You could also just add an if statement around your test if there are few enough of them (e.g. int(sys

Re: [sage-devel] Re: Minimum Python version to 3.8

On Thu, May 13, 2021 at 6:09 AM Dima Pasechnik wrote: > On Thu, May 13, 2021 at 1:34 AM 'Travis Scrimshaw' via sage-devel > wrote: > > > > Own tag might be a goood way forward as the code itself can run on > Python 3.7 by avoiding the multiprocessing. It would be purely to state > that we don't

[sage-devel] Threading and cypari

Upgrading Sage from 9.2 to 9.3 breaks the LMFDB (segfaults on startup). We believe that the problem arises from an interaction between Pari and threads, and were able to duplicate it in Sage with the following: from concurrent.futures import ThreadPoolExecutor sage: with Th

Re: [sage-devel] Threading and cypari

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 this is tested. > > It would be nice to > > 1) reproduce the segfault outside of sage only using python and > cypari2 > > 2) o

Re: [sage-devel] Sage 9.4.beta0 fails to build on MacOS 10.15.7

Can you outline the steps you're taking from the beginning? I think Dima is suggesting that the only reason that you'd see [sage_docbuild-9.4.beta0] is if you used `make` rather than `make build`. David On Mon, Jun 7, 2021 at 7:10 PM Paul Masson wrote: > That's precisely what I'm doing! > > On

Re: [sage-devel] Sage 9.4.beta0 fails to build on MacOS 10.15.7

e documentation, since this upgrade won't add new > features to the viewer. > > On Monday, June 7, 2021 at 5:33:20 PM UTC-7 David Roe wrote: > >> Can you outline the steps you're taking from the beginning? I think Dima >> is suggesting that the only reason that you&#x

Re: [sage-devel] Adèles and ideles: choosing a category

My vote would be for a similar category to the p-adics: sage: Zp(5).category() Join of Category of complete discrete valuation rings and Category of infinite sets and Category of complete metric spaces sage: Qp(5).category() Join of Category of complete discrete valuation fields and Category

Re: [sage-devel] Bug with subgroup method?

I agree that this is a bug. There are several issues, and I don't know if there's an easy fix. 1. The elements of the enumeration are produced by passing in exponent vectors in terms of the generators of H: sage: H([1]) f sage: H([1])^3 1 It's unfortunate that we choose the same letter to represe

Re: [sage-devel] proposal - remove gcc, gfortran, python building/spkgs

I'm not that well informed of the consequences, but I'm generally supportive of removing gcc and (especially) gfortran. We should point people at other resources to get a functional compiler if there's an issue. I also give Dima's opinions on this a lot of weight, since I've seen him answer quest

Re: [sage-devel] Bug with subgroup method?

H.0 is Sage notation for the 1st generator of H. sage: preparse("H.0") 'H.gen(0)' As for getting the value, it depends on what kind of element you have. sage: H.0._exponents (2,) sage: H.0.value() 2 sage: H([1])._exponents (1,) sage: H([1]).value() Traceback (most recent call last): ... Attr

Re: [sage-devel] Re: Library code returning int value

I think it's fine to include a discussion of this in the developer's manual: functions should return an integer rather than an int unless there is a good reason not to (mandated by the language for __len__, to reduce overhead for some internal functions). David On Mon, Jul 12, 2021 at 3:26 AM Kwan

Re: [sage-devel] Re: Vector spaces with immutable vectors by default

I think Nils' original solution, of adding an immutable keyword option to the parent, is a good one. I've run into a similar issue with matrices, where I had to make them immutable before using them as dictionary keys. David On Fri, Aug 6, 2021 at 7:39 PM Nils Bruin wrote: > On Friday, 6 August

Re: [sage-devel] Vector spaces with immutable vectors by default

I actually like this idea a lot. My main concern is that it may not be immediately clear where a hash is being called for a user (for example, using it as an argument to a @cached_method will call __hash__). So when they try to mutate the vector/matrix and it fails, it may be difficult for them t

Re: [sage-devel] Remove nose package?

I don't have a strong opinion on whether to drop nose or not, but I was curious how it was used in Sage. It looks to be required to run tests for networkx, cvxopt and symengine. Will tests for those packages just need to be run after installing nose manually? David On Wed, Sep 29, 2021 at 5:35 P

Re: [sage-devel] Sage crashes when attempting to coerce Magma element to boolean

See https://trac.sagemath.org/ticket/32602. David On Tue, Oct 19, 2021 at 1:02 AM Daniel Hast wrote: > I think I've found a bug in Sage's interface to Magma: Attempting to > coerce a Magma element into a Python boolean causes Sage to crash with a > stack overflow error. > > To reproduce, start S

Re: [sage-devel] Re: Stieltjes constants and ARB

For me, RBF(stieltjes(1)) succeeds on sage-9.4 on linux and fails on sage-9.4-beta4 on OS X with the following error: TypeError Traceback (most recent call last) in > 1 RBF(stieltjes(Integer(1))) ~/sage/sage-9.4.beta0/local/lib/python3.9/site-packages/sage/str

Re: [sage-devel] is coersion always tried in conversion code?

I'm not following the discussion on that ticket completely, but it's hard to see a situation where there'd be a speed benefit to trying coercion first. Here's why: Given two parents A and B, if you try to convert an element of A into B Sage computes and stores a convert map. However, in order to

Re: [sage-devel] A naming question for an enumerator

On Thu, Jan 24, 2019 at 1:27 PM Simon Brandhorst wrote: > So here is a question which came up in #24889: > > We have an enumerator of objects, let us call them breeds of dogs which > returns all breeds with user defined properties e.g. breeds of small dogs. > How would you give the user access to

Re: [sage-devel] Poll: set online=True as the default for threejs viewer

On Mon, Feb 11, 2019 at 12:31 PM Eric Gourgoulhon wrote: > Hi, > > As pointed out in the Free Computational Mathematics > conference today, the > default value of the "online" option of the threejs 3d viewer is False. > This allows for the rendering wi

Re: [sage-devel] Reporting bug：the errors about method "is_trivial() in module sage.rings.ideal"

I agree that this is a bug; are you able to open a ticket? The problem is that ideals in Z[x] use the generic ideal code, which defines equality based on just comparing ordered lists of generators. I think the right thing to do is to change that definition to the normal definition of equality of

Re: [sage-devel] Polyhedron.vertices() function call behaviour

You probably want deepcopy. That being said, Q.vertices should probably also make a copy before returning the result. David On Thu, Apr 11, 2019 at 1:48 AM Narayanan Narayanan wrote: > > I have recently created a Polyhedron Q that corresponts to the cuts of a > graph. > > Once I have Q, I crea

Re: [sage-devel] Change complex number symbols

Is this what you're looking for? sage: z = ComplexNumber(1,2) sage: z 1.00 + 2.00*I sage: print z.str(istr='j') 1. + 2.*j I don't think there's a global way to do this in Sage. I'm also not quite sure which kind of complex number you're wor

Re: [sage-devel] Change complex number symbols

the symbolic ring sage: 3 + 4*j 4*I + 3 sage: Q. = QuadraticField(-1) # for an exact version sage: 3 + 4*j 4*j + 3 RJF > > On Friday, April 12, 2019 at 1:39:51 AM UTC-7, David Roe wrote: >> >> Is this what you're looking for? >> >> sage: z = ComplexNumber(1,2) &

[sage-devel] Factoring bug in Pari stack

I've run across a strange bug that seems to be hardware dependent: it is repeatable on an Ubuntu server, but I can't replicate it on my Macbook Pro or on Cocalc. It occurs when factoring rational polynomials, and gives an error message from pari: "bug in gerepile, significant pointers lost, please

Re: [sage-devel] p-adic analytic functions

On Thu, Jun 20, 2019 at 1:55 PM Kannappan Sampath wrote: > Hello everyone -- > > I am trying to do the following computation --- > > Suppose that h(z) is a polynomial defined over an extension of the 23-adic > integers with unit constant term h(0) and that the uniformizer divides > h(z)-h(0). "By

Re: [sage-devel] Re: Completions of NumberFields at non-archimedean primes

I hope to work on completions with Julian Ruth and Xavier Caruso later this summer. Some functionality is available through Julian's valuation package, but there's work to be done still. I'll write more once I'm not on a bus. :-) David On Fri, Jun 21, 2019 at 12:58 AM Kannappan Sampath wrote:

Re: [sage-devel] Re: Poll: three.js as the default 3d viewer in Sage

+1 for threejs as default. David On Mon, Sep 23, 2019 at 7:24 PM Travis Scrimshaw wrote: > +1 for making the default threejs. > > Best, > Travis > > On Monday, September 23, 2019 at 9:51:23 PM UTC+10, Eric Gourgoulhon wrote: >> >> Dear Sage-dev, >> >> This is a poll to make three.js (https://thr

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

The reason that the warning isn't printed is that the stacklevel is set to 4 by default in order to tell the user where the Integer('012') is occurring. When you type '012' directly into the command line, the stack isn't deep enough and no warning is printed. You do see a warning if you write a f

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

2019 at 4:45 AM Simon King wrote: > Hi David, > > On 2019-10-19, David Roe wrote: > > I think the idea is that if a user's typing interactively then they don't > > need a deprecation warning (since the behavior currently works). It's > more > > im

Re: [sage-devel] Re: [sage-support] Error in operations of finite field

The issue is that you redefined x after defining K. I wrote more on the ticket. David On Fri, Nov 22, 2019 at 1:57 AM Dima Pasechnik wrote: > This is a variable name clash. Somehow, using 'x' for modulus creates a > problem. > If I instead do > > T.=GF(2)[] > K.=GF(2^6, modulus=xx^6 + xx^4 + xx

Re: [sage-devel] Re: Sage 8.9 build fails on macOS Catalina

Hi all, I have a new laptop running OS X 10.15 and haven't been able to successfully build Sage 9.0.beta9 on it. I used Apple's Migration Assistant to move everything from my old laptop (which was running a much older version of OS X), so I wouldn't be surprised if there were some leftover settin

Re: [sage-devel] Re: drop python2 compatibility in 9.1 ?

I just added a 9.2 milestone on trac, which isn't the default. David On Sun, Jan 5, 2020 at 4:37 PM John H Palmieri wrote: > Can someone with trac admin access and know-how add a 9.2 milestone, so > people can develop for 9.2 if they want to focus on dropping Python 2 > support? > > Meanwhile, 9

[sage-devel] Porting .sage files to sage-9.0

I had a recent discussion asking if there are any good tools for porting Sage code to Python 3. Given the recent discussion about how long we support Python 2, it seems like one concrete step we can take to help users is to provide s

Re: [sage-devel] optional tag for sage versions (doctest)

On Fri, Jan 10, 2020 at 1:16 PM Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Dear all, > > I do maintain Python libraries that depend on Sage and uses the > Sage doctest framework. I do my best so that the libraries > install and work on older versions of Sage. However, some features > a

Re: [sage-devel] Coercions of polynomials

On Tue, Jan 14, 2020 at 2:31 AM Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Maybe you want > > sage: T(S.flattening_morphism()(f)) > a*x + b*x + a*y + b*y > > > Le 14/01/2020 à 08:22, Travis Scrimshaw a écrit : > > Hi everyone, > > I wanted to know if this is a deliberate behavior o

Re: [sage-devel] Coercions of polynomials

feel the default should be to go into the base ring rather > than the final ring, but another option would be to just error out and say > it is ambiguous. > I think an error is best. Users can always use lists if they really want to do something like this. David > > Best, > Travi

Re: [sage-devel] Power series do not distinguish between different precisions!

We only store power series and p-adics to finite precision, so it's impossible to tell whether the mathematical objects underlying two elements in Sage are actually equal. In practice, the goal of a p-adic or power series computation is to determine some result approximately, since that's all that

Re: [sage-devel] How to deal with unsorted output of dictionaries in doctests

On Mon, Jan 27, 2020 at 5:01 PM Nils Bruin wrote: > For 2) there are different possibilities. > a) Something like sorted(D.iteritems()) works, but it means the doctest > now displays a list of tuples rather than something that looks like a dict: > not a problem for "TESTS:" but less than desirab

Re: [sage-devel] Re: Unable to build sage after git trac config

On Thu, Jan 30, 2020 at 7:35 AM Simon King wrote: > Hi Eric, > > On 2020-01-30, Eric Gourgoulhon wrote: > > I would even vote for removing the git-trac section from the developer > > manual. > > -1 > > I do use "git trac". > Agreed. I would absolutely not advocate removing git-trac from the ma

Re: [sage-devel] Re: Build does not complete for "sage -i database_cremona_ellcurve"

On Thu, Feb 20, 2020 at 5:32 PM 'Klaus Krtschil' via sage-devel < sage-devel@googlegroups.com> wrote: > Sage is working perfectly. The installation of this package triggers a lot > of compiles. After the error happens Sage still works normally. > Did you originally install your sage from a binary

Re: [sage-devel] Re: Build does not complete for "sage -i database_cremona_ellcurve"

; > Am Donnerstag, 20. Februar 2020 23:41:28 UTC+1 schrieb David Roe: >> >> >> >> On Thu, Feb 20, 2020 at 5:32 PM 'Klaus Krtschil' via sage-devel < >> sage-...@googlegroups.com> wrote: >> >>> Sage is working perfectly. The install

Re: [sage-devel] Inherit Method but keep Documentation?

On Wed, Mar 18, 2020 at 10:58 PM Michael Jung wrote: > Damn it. Then I another question: Would it cause a slow-down if I > overwrite the method with something like > > def my_method(self): > r""" > New Documentation > """ > Mother.my_method(self) > > This will take small amount of

Re: [sage-devel] An issue related to the construction of elliptic curves over tower extension fields

I have been working on https://trac.sagemath.org/ticket/28485, which I think should solve this issue. I've gotten distracted by other projects, but will try to get back to it. The idea is to use the infrastructure introduced in #21413 (merged in an early sage-9.1 beta) to create relative extensio

Re: [sage-devel] vector subspace of K^30 where K is a nf of degree 20

For matrices over Q there's sage.matrix.misc.matrix_rational_echelon_form_multimodular, which is the default for matrices with more than 25 rows/columns. It should be possible to adapt this to number fields. You might also look into what Pari is capable of, since we're getting our number fields f

Re: [sage-devel] Re: Proposal for Sage 9.2: require "./configure" before "make"

On Sun, Apr 19, 2020 at 9:49 AM Dima Pasechnik wrote: > On Sun, Apr 19, 2020 at 9:32 PM 'Jonathan Kliem' via sage-devel > wrote: > > > > Will this speed up the `make build` or `sage -br` process? It used to be > really quick, but now it takes much longer and rechecks all the packages. > > exactl

Re: [sage-devel] Pillow built without jpeg support in Sage 10.2.rc3

I'm not aware of why we were suppressing jpeg support before, but this sounds like a good idea to me. David On Thu, Nov 16, 2023 at 9:48 AM Eric Gourgoulhon wrote: > Hi All, > > Pillow provides the Python Imaging Library (PIL) > https://pillow.readthedocs.io/en/stable/ > and is a standard packag

[sage-devel] gcc problems on MacOS

I'm trying to build Sage 10.2.rc4 on MacOS 13.3.1 and have been running into multiple errors, some possibly due to Apple upgrading my OS when my laptop went in for repair. I've managed to get past all of Sage's dependencies, and am currently stuck on an error in sagelib: g++ -std=gnu++11 -std=gnu

Re: [sage-devel] Re: gcc problems on MacOS

^ > :433:6: note: expanded from here > GCC error "'fmpz_poly_scalar_mul_mpz' is deprecated. Use > 'fmpz_poly_scalar_mul_fmpz' instead." > ^ > > Your config.log says that you are using flint from SPKG. Above

[sage-devel] Policy for disputed PRs: discussion

Hi all, I'm writing about an issue that I think is causing substantial harm to the Sage community: the only current mechanism we have for resolving a disagreement is to call a vote on this email list. There are certainly times where this is an appropriate response, and I think it's still reasonabl

Re: [sage-devel] Re: Policy for disputed PRs: discussion

Let's try to focus on the policy proposal, rather than specific disagreements on individual PRs. Dima, I'm sorry that you're feeling frustrated with the whole process. It may be helpful to have additional directions about the overall strategy for Sage's build system, but that's better put off to

Re: [sage-devel] Application for NumFOCUS affiliation of SageMath

I agree with Dima that 2 days is not enough time to gather feedback. Is there any reason for the quick turnaround time? David P.S. I'm sorry about disappearing from the other thread about disputed PRs. I will try to summarize the discussion on that thread and call for a vote shortly. On Sat, Jan

Re: [sage-devel] Re: Implementing minimum_generating_set() function

You can lift elements via the quotient map to get representatives of each coset. I'm not sure that this is wrapped in Sage, but using gap directly you have: sage: Pgap = p._libgap_() sage: Ngap = N._libgap_() sage: phi = Pgap.NaturalHomomorphismByNormalSubgroup(Ngap); phi [ (2,3,4,5,6,7) ] -> [ f

Re: [sage-devel] Unify error for trying to invert non-invertible elements

I agree that there are cases that shouldn't be changed to an ArithmeticError, and that grepping for "invertible" isn't sufficient. But I think with a narrower scope this change is a good idea: if the error arises from attempting to invert a non-invertible element of a ring. So +1 from me, with a

Re: [sage-devel] Unify error for trying to invert non-invertible elements

On Thu, Feb 8, 2024 at 8:18 PM 'Travis Scrimshaw' via sage-devel < sage-devel@googlegroups.com> wrote: > For RuntimeError, I would make it sound like it tells you there is serious > error occurring as it doesn't fall into any other error categories. This > actually makes it the opposite of a catch

Re: [sage-devel] Re: Disputed Pull Requests / Role Sage-Abuse and the Code of Conduct

can confirm that the google group list does receive messages. > And if so, may we know who's on the committee? > > Asking on behalf of the community. > The members of the committee are: * William Stein * Vincent Delecroix * David Joyner * Harald Schilly * John Palmieri * David Roe

Re: [sage-devel] Bug in finding generators of elliptic curves over a quadratic domain

The problem is in the definition of avoid. There was an assumption made that the discriminant would be integral, so any(q.divides(m) for m in avoid) has avoid = [1048576/5764801, 8, 28, 49, 7] If you change the definition of avoid from avoid = [self._N, self._D] + [P[0].denominator_ideal().norm()

Re: [sage-devel] Re: Unload "blocker" label

On Mon, Feb 26, 2024 at 8:06 PM John H Palmieri wrote: > I think that usage (1) is the correct use of "blocker," and usage (3) is > not. Usage (2) should have a new name, as Vincent proposes. Failing that, > this new use of "blocker" must be documented in > https://doc.sagemath.org/html/en/develo

[sage-devel] Looking for volunteers

ge-ab...@googlegroups.com. I announced the membership of this committee a few days ago in another thread; since then one member has resigned and another has expressed willingness to be replaced. The current membership is William Stein John Palmieri David Roe Vincent Delecroix David Joyner As a group, we believe

[sage-devel] Labels and Reviewing

Dear Sage developers, The conflicts we've seen in the last several months are multifaceted, but one of the central issues at hand is how we decide what code is incorporated into Sage through our review process. I have two goals for this thread: to describe our current standards (as codified in the

Re: [sage-devel] Re: Labels and Reviewing

On Wed, Feb 28, 2024 at 1:01 AM Kwankyu Lee wrote: > Thank you for making progress on these urgent issues. I suggest the > following: > > 1. Open two other new threads, each of which is for voting on each > proposal. > 2. On a proposal, it should be clear that *a positive vote (+1) is for > the w

Re: [sage-devel] Looking for volunteers

On Wed, Feb 28, 2024 at 10:51 AM Dima Pasechnik wrote: > >> We propose the following voting system. >> 1. A nomination period of 1 week, where any Sage developer can nominate >> someone to serve on the committee by emailing sage-ab...@googlegroups.com. >> You are allowed to nominate yourself (and

Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

Thank you for starting the conversation Martin. I certainly think that all of these suggestions are appropriate to discuss, and that sage-devel is probably a better venue for discussion like this than the PR. On Fri, Mar 1, 2024 at 5:49 AM 'Martin R' via sage-devel < sage-devel@googlegroups.com>

Re: [sage-devel] Permissions on github

As far as I can tell, you need some kind of admin privileges in order to add people to Triage (which is unfortunate, since membership in this team is critical for our reviewing process). The method that I use is to go here and click on the big green

[sage-devel] VOTE: disputed PRs

With no further discussion on this thread , I'm calling a vote on a new process for resolving disagreements on a PR. *Proposal* It is now allowed to vote on disputed PRs directly on Github rather than bringing them to sage-devel. Working thing

[sage-devel] VOTE: Use "CI Fix" label for merging into continuous integration runs

The following proposal has been made several times the last few weeks: in PR #37428 , in this thread and then in this thread . It is orthogona

Re: [sage-devel] Looking for volunteers

We've received several nominations, but if you have been on the fence about suggesting someone I encourage you to write to us. The nomination period will close tomorrow night. David On Wed, Feb 28, 2024 at 10:52 AM David Roe wrote: > > > On Wed, Feb 28, 2024 at 10:51 AM Dima Pa

[sage-devel] Vote: Sage Code of Conduct

ippela...@gmail.com, jplab on github) John Palmieri (jhpalmier...@gmail.com, jhpalmieri on github) Viviane Pons (vivianep...@gmail.com, VivianePons on github) David Roe (roed.m...@gmail.com, roed314 on github) Julian Rüth (julian.ru...@fsfe.org, saraedum on github) William Stein (wst...@gmail.com, willia

Re: [sage-devel] Re: Labels and Reviewing

blockers > (e.g. we have a plenty of outstanding symbolic integration bugs). > That is, unless it's absolutely Earth-shuttering, don't use "blocker". > > Dima > > >> >> On Wednesday, February 28, 2024 at 6:08:20 AM UTC David Roe wrote: >> >>

Re: [sage-devel] Re: Labels and Reviewing

Dear Sage developers, Dima is correct that there are several developers who have blocked each other. The Sage Code of Conduct Committee is aware of several cases and is working on resolving them. We believe both that the presence of these blocks is harming the Sage project, and that it can be app

Re: [sage-devel] Google Season of Docs – org application deadline April 2

I think this would be good for Sage. I think there are several decisions to be made: * What are our most pressing documentation needs? Personally, I think we have a gap between the reference manual (which is extensive but has no flow) and the thematic tutorials (which are written to tell a story

Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

I agree with both Tobias and Matthias that we should have a discussion about the roles of maintainers (since they have defined privileges on github) and changes to Sage's governance model more generally. Martin and Tobias have commented on trying to include some additional principles into the code

Re: [sage-devel] Re: Application for NumFOCUS affiliation of SageMath

I support Matthias' initiative to join NumFocus. Looking at the application , there are only a few todo items: * Describe the shared history with Cython and IPython. This doesn't need to be extensive, but would be useful. * If we update the code of

Re: [sage-devel] Re: Sage's Code of Conduct: proposed changes

1987309496> that these kinds of guidelines are better put in our reviewing code rather than the Code of Conduct, since they feel more like details than guiding principles. David > David Roe schrieb am Sonntag, 10. März 2024 um 16:44:06 UTC+1: > >> I agree with both Tobias and Matthia

Re: [sage-devel] Google Season of Docs – org application deadline April 2

le to rewrite it properly (yes, I will >> create an issue for this soon!) >> >> John >> >> On Sun, 10 Mar 2024 at 15:03, David Roe wrote: >> >>> I think this would be good for Sage. I think there are several >>> decisions to be made: >>> * W

Re: [sage-devel] Re: Help and Advice | Arithmetic of Jacobians in the Split/Real Model is Broken

There is also this old trac ticket about implementing fast arithmetic in genus 2 Jacobians, which never made it into Sage. I've CCed Mike Jabobson, who worked on it. David On Tue, Mar 12, 2024 at 12:10 PM Giacomo Pope wrote: > Thank you for linki

Re: [sage-devel] Re: VOTE: disputed PRs

The vote has passed. There are currently 36 open disputed PRs . Given the extensive comments on some of these PRs, I would agree that we should follow some version of Karl-Dieter's suggestion. In particular, while the author of the PR remains aut

Re: [sage-devel] Re: VOTE: disputed PRs

Sorry for the delay in responding; I have had much time today. The code of conduct committee's intention in changing the status on some of the disputed tickets was to note ways in which participants had not followed our previous standards for setting review status. At this point, given the policy

[sage-devel] Re: Vote: Sage Code of Conduct

(vivianep...@gmail.com, VivianePons on github) David Roe (roed.m...@gmail.com, roed314 on github) Julian Rüth (julian.ru...@fsfe.org, saraedum on github) Thank you to everyone for voting! I also want to thank Vincent Delecroix, David Joyner, Harald Schilly, and William Stein for their service on

Re: [sage-devel] "Disputed" PRs: Please vote, it matters

I will echo Matthias here. We just spent multiple months working out this new process. In order to make it work, people need to help make judgements about which of these PRs should proceed and be included in Sage. I understand that participating in these particular PRs can be daunting: the peopl

Re: [sage-devel] Re: Vote: Sage Code of Conduct

On Mon, Mar 18, 2024 at 11:10 AM Dima Pasechnik wrote: > It's very important to note that with multiwinner approval voting, merely > counting the votes per candidate and picking the top ones can lead to > rather unfair results > (unlike in the single winner case). > > For instance, if we elect k=

Re: [sage-devel] Re: VOTE: Use "CI Fix" label for merging into continuous integration runs

This vote has passed, and I've added a "CI Fix" label on github. I am not going to have time to implement changes to our CI infrastructure in the near future, but others are welcome to do so. David On Sun, Mar 10, 2024 at 1:37 PM seb@g

Re: [sage-devel] Re: Vote: changes to Sage's Code of Conduct

+1. On Thu, Mar 21, 2024 at 4:09 PM 'Martin R' via sage-devel < sage-devel@googlegroups.com> wrote: > +1 > > I just re-read the whole thing, and I'm quite impressed! Thank you! > > On Thursday 21 March 2024 at 19:03:34 UTC+1 Matthias Koeppe wrote: > >> +1. >> >> On Thursday, March 21, 2024 at 9:

Re: [sage-devel] Urgent: Please vote on these "disputed" PRs

We have received messages from several people that the level of discord on display between Dima and Matthias makes them feel uncomfortable participating on this email list. To protect the community from this acrimony, we are for now restricting Dima and Matthias to moderated contributions on sage-d

Re: [sage-devel] (Re-)building an inclusive SageMath community. II: Recognizing and fighting abuse, bullying, disrespect

community is currently falling short, even if you do not have specific solutions. The Sage Code of Conduct Committee David Roe J-P Labbe John Palmieri Julian Rüth Nils Bruin Viviane Pons On Fri, Apr 12, 2024 at 4:11 PM Matthias Koeppe wrote: > Trigger Warning: In this post, I will discuss top

Re: [sage-devel] Re: Proposal (redo): Make python_build (and its dependency pyproject_hooks) a standard package

On Mon, Apr 15, 2024 at 5:50 PM Dima Pasechnik wrote: > > > On Mon, Apr 15, 2024 at 10:01 PM François Bissey > wrote: > >> >> >> On 16/04/24 04:41, kcrisman wrote: >> > SageMath has several other long-term contributors who also package >> > software. We're all roughly on the same page ab

[sage-devel] VOTE: Revert merged PR with unreviewed dependencies

Hi all, Sage has had a review process for over 15 years, but a combination of recent changes has led to the merging of a PR into sage-10.4.beta3 of a change (#36964 ) that I believe should not (yet) have been merged. In #37796

Re: [sage-devel] Re: VOTE: Revert merged PR with unreviewed dependencies

efinition, #36951 and #36676 did not have positive review at the time that #36964 was merged. David On Thursday, April 18, 2024 at 8:54:26 AM UTC-7 David Roe wrote: > >> Hi all, >> Sage has had a review process for over 15 years, but a combination of >> recent changes has l

Re: [sage-devel] Re: VOTE: Revert merged PR with unreviewed dependencies

0:47:36 AM UTC-7 David Roe wrote: > >> On Thu, Apr 18, 2024 at 1:43 PM Matthias Koeppe >> wrote: >> >>> I will first note that the title of this post is misleading. >>> Everything that was merged has been reviewed -- as noted, many months >>> ago.

Re: [sage-devel] VOTE: Revert merged PR with unreviewed dependencies

gt; >>> >>> -1 >>> >>> If something has been done that should be undone, I very much trust >>> Volker to take care of it when he can, without the need for endless >>> time-consuming discussions and votes. >>> >>> Best, >>&

<    4   5   6   7   8   9   10   >