[sage-devel] Download-statistics of Sage related PyPI packages

I queried such data stored between January 2016 and April 2023 and put it into a read-only SQLite database. If you're interested, check out this DBHub database . Scroll down to read how to visualize the data. I used a Google free trial

Re: [sage-devel] Re: Can I build Sage via MacPorts under MacOS 10.9?

Aha – thank you! I will start playing with this... – Louis On Monday, May 22, 2023 at 12:17:56 PM UTC-4 Dima Pasechnik wrote: > On Mon, May 22, 2023 at 4:53 PM Dima Pasechnik wrote: > > > > On Mon, May 22, 2023 at 3:09 AM Louis Deaett > wrote: > > > > > > Many thanks for the word of encoura

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

On Fri, 2023-05-26 at 18:15 +0100, Oscar Benjamin wrote: > > What is wrong with Sage just saying that an older version of an > operating system only works with an older version of Sage? Matthias alluded to this when he mentioned that we only have one release branch of sage. Our version numbers ar

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

On Friday, May 26, 2023 at 9:19:52 AM UTC-7 Dima Pasechnik wrote: On Fri, May 26, 2023 at 5:01 PM Matthias Koeppe wrote: > > d) In contrast, our uses of NumPy/SciPy in the Sage library are very basic > > and dating back by about a decade; > No, not true. E.g. > schemes/riemann_surfaces/riem

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

On Fri, 26 May 2023 at 16:19, William Stein wrote: > > On Fri, May 26, 2023 at 7:57 AM wrote: > > > a) Sage has a dual role as a library ("project") and as a distribution. > > > NEP > > > 29 was designed for projects, and not for software distributions. > > > > No, Sage is just a project, with l

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

> I have the impression that NEP 29 tried to very rigidly define end of life by a specific timeline with no flexibility for the potential that the official Python release timelines are not rigid and fixed in stone forever The PR linked above mentions quite often that they do take variations/c

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

Here is the PR that introduced NEP 29: https://github.com/numpy/numpy/pull/14086. The main discussion happened in person at scipy 2019 and in webcalls. But a lot of the points raised here are answered in this PR. For example, the point about Linux LTS / Python EOL is addressed by one of the wr

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

On Fri, May 26, 2023 at 9:19 AM Dima Pasechnik wrote: > Please admit it, otherwise. I don't see a way to continue a discussion with > you. Can you please continue to engage, but view this as a public debate for the benefit of all sage developers, rather than a discussion with Matthias? It's a

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

On Fri, May 26, 2023 at 5:01 PM Matthias Koeppe wrote: > > On Friday, May 26, 2023 at 7:57:53 AM UTC-7 dim...@gmail.com wrote: > > On Fri, May 26, 2023 at 06:34:25AM -0700, Matthias Koeppe wrote: > > I am voting NO. > > > > I. This proposed policy change does not solve any problem. There are no >

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

On Friday, May 26, 2023 at 7:57:53 AM UTC-7 dim...@gmail.com wrote: On Fri, May 26, 2023 at 06:34:25AM -0700, Matthias Koeppe wrote: > I am voting NO. > > I. This proposed policy change does not solve any problem. There are no > problems whatsoever with how we have managed the support of Pytho

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

On Fri, May 26, 2023 at 7:57 AM wrote: > > a) Sage has a dual role as a library ("project") and as a distribution. NEP > > 29 was designed for projects, and not for software distributions. > > No, Sage is just a project, with lots of dependencies (way too many). > It's not a software distribution

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

Hi, To help with people who want to make an informed decision, is there any public discussion of the original NEP 29 proposal? The only thing I could find was this post from Sebastian Berg, where he says at https://mail.python.org/pipermail/numpy-discussion/2019-October/080128.html "We propose

Re: [sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

On Fri, May 26, 2023 at 06:34:25AM -0700, Matthias Koeppe wrote: > Thanks, Tobias, for opening this vote thread. Here on sage-devel, this is a > much better setting than what you attempted > in https://github.com/sagemath/sage/pull/35404#issuecomment-1504474945 > > I am voting NO. > > There's a

[sage-devel] Re: Follow NEP 29: Recommended Python version

For easy reference: Tobias has proposed a vote on this question in the sage-devel thread https://groups.google.com/g/sage-devel/c/3Zoq0CNE1hE On Friday, February 24, 2023 at 7:10:07 PM UTC-8 Tobias Diez wrote: > Hi all, > > I propose to follow the NumPy enhancement proposal 29: "Recommend Pyt

[sage-devel] Re: VOTE: Follow NEP 29: Recommended Python version

Thanks, Tobias, for opening this vote thread. Here on sage-devel, this is a much better setting than what you attempted in https://github.com/sagemath/sage/pull/35404#issuecomment-1504474945 I am voting NO. There's a simple rationale: I. This proposed policy change does not solve any problem.

[sage-devel] bug in invariants_of_degree

I need help with https://github.com/sagemath/sage/issues/35684 Is Ben Hutz still around? Martin -- 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 sage-devel+unsub

Re: [sage-devel] VOTE: Follow NEP 29: Recommended Python version

I am for adapting NEP 29 for Sage (and thus dropping Python 3.8 now). Few comments on the Summary: 2) it's very important to be in sync with various Sage's upstream parts, as much as possible. We don't want to lag behind, preventing us from being able to use latest versions. 3) Saying that Pytho

[sage-devel] VOTE: Follow NEP 29: Recommended Python version

Dear Sage developers, the NumPy enhancement proposal 29: "Recommend Python and Numpy version support as a community policy standard" (available at https://numpy.org/neps/nep-0029-deprecation_policy.html) specifies when it's okay to drop support for old Python version. Namely, a release should