Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On Fri, Apr 18, 2025 at 4:12 PM Nils Bruin wrote: > > On Friday, 18 April 2025 at 10:07:12 UTC-7 dim...@gmail.com wrote: > > Nobody is going to "break" anything. You'll just need a proper Python to > install Sage, like one of many pre-reqs already needed. > It's just fear-mongering. Building Sage

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On Sat, Apr 12, 2025 at 8:48 PM Marc Culler wrote: > > On Saturday, April 12, 2025 at 9:57:50 PM UTC-5 Dima wrote: > > this is what many users need - to be able to install Sage into an existing > Python environment; thus support is provided for a range of pythons. > > > That is what I said in my

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

I regularly build proper multiarch (so x86 and arm) Sage Docker containers, e.g., https://hub.docker.com/repository/docker/sagemathinc/sagemath/general https://hub.docker.com/orgs/sagemathinc/repositories -- William On Wed, Apr 9, 2025 at 10:00 PM 'Nasser M. Abbasi' via sage-devel wrote: > >

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

> On Wed, Apr 9, 2025 at 2:37 PM Nils Bruin wrote: >> Quite frankly, things like conda and uv are great initiatives and it would >> be great for sage to work nice with them. Conda is getting quite mature and >> has a wide user base, so transitioning to depending on conda may be a >> reasonable

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

> I believe that Homebrew wouldn't work because of the issue with rpaths that > Marc hints at earlier in his message -- in particular the paths are baked in > as /opt/homebrew/* and will not survive relocation. The "uv" installer can > install in varying locations, but I'm not sure the result i

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On Sun, Apr 6, 2025 at 11:40 AM Dima Pasechnik wrote: > On 6 April 2025 11:41:21 GMT-05:00, Nils Bruin wrote: > >It looks to me that there are two points of view here. > > > >1) Having sagemath detect python version requirements and build its own if > >not acceptable version is found leads to inc

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On Fri, Apr 4, 2025 at 8:50 AM Dima Pasechnik wrote: > > On Thu, Apr 3, 2025 at 5:48 PM Marc Culler wrote: > > > > This will unnecessarily make it more difficult to build the Sage_mac OS > > binary package. In order to make that package easy to install in the way > > that normal macOS users e

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On Thu, Apr 3, 2025 at 7:06 PM Trevor Karn wrote: > > Maybe we can all take a breath here. Everyone here is passionate about making > Sage as good as it can be. This seems to be getting a bit too heated right > now. > +1 - I just wanted to offer some helpful links and support, and now I feel l

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On Thu, Apr 3, 2025 at 3:48 PM Marc Culler wrote: > > This will unnecessarily make it more difficult to build the Sage_mac OS > binary package. In order to make that package easy to install in the way > that normal macOS users expect, it must be signed and notarized. In order to > notarize t

Re: [sage-devel] SageMath Now Supports Meson – Faster and More Efficient Builds!

Tobias, Congrats and fantastic! Is it possible that you could add some additional "human context" for those of us on the sidelines, e.g., who added Meson support to Sage (you?), why?, how hard what is and how long did it take?, what was involved? Also, to what extent does Meson replace autotool

Re: [sage-devel] PROPOSAL: remove python3 spkg from Sage

On Wed, Apr 2, 2025 at 8:38 AM 'tobia...@gmx.de' via sage-devel wrote: > > Sounds like a good idea. Installing a specific version of Python nowadays is > easy enough and there a few tools that make this experience as smooth as > possible. For example, uv uses prebuild pythons for many OS to spee

Re: [sage-devel] Are there plans to try to reduce the inner inconsistencies in sage?

Georgi, Also, you can browse all of the currently 5006 open "plans" for Sage here: https://github.com/sagemath/sage/issues -- William On Fri, Jan 3, 2025 at 7:07 AM Dima Pasechnik wrote: > > > On 3 January 2025 03:00:20 GMT-05:00, Georgi Guninski > wrote: > >In sage 10.4, I can prove $-1 =

Re: [sage-devel] Installing 32-bit Linux on an old laptop

On Sun, Dec 15, 2024 at 6:14 AM John Cremona wrote: > Well I am giving up on using my 20+-year-old hardware. I have made many > attempts to install a 32-bit distro (debian, MX, Mint) but all failed -- in > the case of Mint, there was kernel panic before it even got going. I did a > 100% success

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

For a timely example of how PyPI size limits can be very real, JupyterLab's is hitting this right now: https://github.com/jupyterlab/jupyterlab/issues/16859 ERRORHTTPError: 400 Bad Request from https://upload.pypi.org/legacy/ Project size too large. Limit for project 'jupyterlab' tot

Re: [sage-devel] `ask.sagemath.org` down (again) ?

On Thu, Oct 10, 2024 at 8:18 AM Dima Pasechnik wrote: > Perhaps we should at least set up a read-only mirror of > ask.sagemath.org somewhere outside Paris? > I volunteer resources for hosting a readonly mirror... > > Dima > > On Thu, Oct 10, 2024 at 8:47 AM Emmanuel Charpentier > wrote: > > >

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

Dima: > If we concentrated on facilitating the latter, rather than on > distribution packages, it could have been there now. > +1 Nils: > I have yet to see a convincing example where chopping up core architecture of sagemath (like the coercion framework, the category framework, etc) leads to usa

Re: [sage-devel] Re: [debian-science] Modularized sagemath packages: proof of concept

Hi, There are a number of big chunks of functionality in Sage, like interval arithmetic (I was just going to say this and Marc beat me to it), and the sage preparser, which could be valuable as separate packages that Sage uses. License of Sage is GPLv3, whereas the vast majority of the scientific

Re: [sage-devel] Suspension of a developer

I had stopped reading the Sage mailing lists due to drama, and am now re-enabling my subscriptions. Thank you, William On Friday, October 4, 2024 at 9:32:13 AM UTC-7 vdelecroix wrote: > It is a very sad news that such measure had to be taken. I fully trust > the committee in its decision

[sage-devel] sage optional packages

Dear Sage Developers, I'm curious about the testing and installation support for the optional packages listed on the SageMath documentation page here . I was wondering if anybody knows more about the extent of testing done for th

Re: [sage-devel] Re: wasm

this functionality. So I thought, perhaps we could look >>> for solutions where Sage is used together with web assembly. >>> >>> After some research I have the impression that there are some proofs of >>> concept, but there is nothing actively developed? >>&g

Re: [sage-devel] Re: conda sage

With switching to Miniforge it is now working for me extremely well. I’m going to be making a new video and tutorial about this soon. Thanks for all you do Isuru! -- William Stein On Wed, Mar 13, 2024 at 9:11 AM Isuru Fernando wrote: > Hi William, > > Let me know if you have any

Re: [sage-devel] stopping cypari2, pari-jupyter and pplpy maintenance

Hi Vincent, To help whoever takes over, do you have any comments about *why* you will not work on any of these projects? Is it just lack of time and you need to focus on something else, or is there something fundamentally annoying about the direction of these projects? Thanks for any insight to

Re: [sage-devel] Re: conda sage

.. On Sun, Mar 10, 2024 at 5:31 PM William Stein wrote: > I was just carefully reading the page about Mambaforge linked to from > Sage, i.e., this page > > https://github.com/conda-forge/miniforge > > and it says that Mambaforge is deprecated and no longer recommended, and > instead

Re: [sage-devel] Re: conda sage

-$(uname)-$(uname -m).sh sh Miniforge3-$(uname)-$(uname -m).sh -b -u -p /conda -- William On Sun, Mar 10, 2024 at 4:05 PM William Stein wrote: > Hi, > > So I was using MicroMamba, whereas that page says Sage only > supports Mambaforge, Miniforge, Miniconda or Anaconda.I tried w

Re: [sage-devel] Re: conda sage

x27;s easy to switch Python versions. So I'll switch from using MicroMamba to Mambaforge. Problem solved. William On Sun, Mar 10, 2024 at 1:47 PM William Stein wrote: > > > On Sun, Mar 10, 2024 at 1:39 PM Matthias Koeppe > wrote: > >> William, do the instructions in

Re: [sage-devel] Re: conda sage

s all instances of the value. set Set a configuration value get Get a configuration value > > > > On Sunday, March 10, 2024 at 12:36:47 PM UTC-7 William Stein wrote: > >> Hi, >> >> I just tried installing sage via co

[sage-devel] conda sage

Hi, I just tried installing sage via conda and it's broken. Am I doing something wrong, or is there any automated testing of sage in conda (which might be a good thing to have)? I was going to publicize sage+conda in a post I was about to make, but won't... 1. Install mambaforge into Ubuntu 2.

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

sion of the initial proposal draft: >> https://github.com/sagemath/sage/wiki/NumFOCUS and I welcome discussion >> here and collaborative editing in the wiki page. >> I'll submit by the next target date (Apr 15). >> >> Matthias >> >> >> On Tuesday,

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

Hi, Related to NumFOCUS, this new proposal for Jupyter to restructure their relationship with NumFocus is possibly relevant: https://jupyter.org/governance/linux-proposal.html William On Sun, Jan 21, 2024 at 12:59 PM Matthias Koeppe wrote: > In case people are interested in a synchronous disc

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

+1 On Mon, Mar 4, 2024 at 8:03 AM Edgar Costa wrote: > +1 > > On Mon, Mar 4, 2024, 10:49 Giacomo Pope wrote: > >> +1 >> >> On Monday, March 4, 2024 at 1:57:48 PM UTC Dima Pasechnik wrote: >> >>> +1 >>> >>> On Mon, Mar 4, 2024 at 8:43 AM David Roe wrote: >>> The following proposal has been

Re: [sage-devel] Re: VOTE: use "blocker" label only for PRs; use "critical" label for Issues

On Wed, Feb 28, 2024 at 8:39 AM Eric Gourgoulhon wrote: > -1 from my side, for I think an issue can be a blocker. > For instance: > https://github.com/sagemath/sage/issues/36914 > This issue, which regards the use of the notebook, could not have been > detected by the CI framework. It is a serio

Re: [sage-devel] Proposal: Make pytest, pytest_xdist, pytest_mock, python_build standard packages

(Also, thanks everyone for so far taking extra effort to be civil when discussing the topic of vendored dependencies, which I know touches a nerve for people.) On Sat, Feb 10, 2024 at 4:36 PM William Stein wrote: > > Hi Dima, > > I believe I'm the person who introduced that lon

Re: [sage-devel] Proposal: Make pytest, pytest_xdist, pytest_mock, python_build standard packages

Hi Dima, I believe I'm the person who introduced that long standing policy. It was indeed motivated by a significant paying customer's requirement to install Sage entirely from source, and without an external network. I believe no such customers have supported the Sage project for about a decade,

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

itive experience for everyone participating in Sage development. Best regards, Volker Braun and William Stein [1] https://github.com/sagemath/sage/pulls?q=is%3Aopen+is%3Apr+label%3Adisputed -- William (http://wstein.org) -- You received this message because you are subscribed to the Google Groups

Re: [sage-devel] Wanted: Unicode testers with PR #36861

ither. -- William On Thu, Dec 14, 2023 at 2:01 PM Dima Pasechnik wrote: > > On Thu, Dec 14, 2023 at 9:30 PM William Stein wrote: > > > > Hi, > > > > Last time I benchmarked things, luatex was sometimes the slowest of > > the three major latex compilers, sometimes by

Re: [sage-devel] Wanted: Unicode testers with PR #36861

Hi, Last time I benchmarked things, luatex was sometimes the slowest of the three major latex compilers, sometimes by a factor of 2. I realize benchmarking could be impacted by things like how exactly Lua was built on the target platform, as part of latex. In any case, for this application, perfo

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

On Thu, Nov 30, 2023 at 12:37 PM John H Palmieri wrote: > To the extent that this specific PR is emblematic of a particular approach > to Sage development (a flawed approach in Dima's view, if I understand > right), then the whole approach should be discussed here. Probably many of > these issues

Re: [sage-devel] Poll: deprecate backslash operator

Again, as the person who added it to Sage in the first place: deprecate. William On Sat, Sep 30, 2023 at 4:02 PM Dima Pasechnik wrote: > > deprecate! > > On Sat, Sep 30, 2023 at 10:47 PM John H Palmieri > wrote: > > > > I asked this already but with a different subject heading, so people may

Re: [sage-devel] Questions about performance of SageMath, and of graph (algorithms) libraries

> To give an explicit and specific example, I'm also interested in graph > algorithms, without calling libraries written in C/C++ or Julia, is it > possible to make graph algorithms faster on very-large graphs with what's > mentioned above? > One relevant Python library is https://github.com/r

Re: [sage-devel] Re: keywords in github

On Fri, Sep 29, 2023 at 4:13 AM kcrisman wrote: > GitHub search is terrible, and I don't understand why. I often (not on this > project) search for words (not just text strings) that I know I present > multiple times in the codebase, and get no results at all. Sort of defeats > the point of a

Re: [sage-devel] Discussion and poll: should Sage Integers have a backslash operator?

Hi, I'm the guilty party who added \ to Sage notation in the first place, and I would definitely vote to *remove* it. I wish I had never added it in the first place. Nils has some very good points! In retrospect, I wish we had a "fully supported" way of using Sage entirely without the preparse

[sage-devel] The EMS/ECMI Lanczos Prize for Mathematical Software

Hi Sage Developers, Jennifer Balakrishnan and I are members of a prize committee for a new prize in "mathematical software", which the Europeans have decided to fund.Here's the call for *self nominations*, and a link to the webpage with more details. I personally think any significant compon

Re: [sage-devel] Re: Ask about the SageMath codebase using ChatGPT

On Sat, Jul 1, 2023 at 2:56 AM Nils Bruin wrote: > > On Friday, 30 June 2023 at 20:41:51 UTC+2 William Stein wrote: > > The point is that instead of using GPT's vague memory of what it might > have seen, this instead uses the actual Sage source code, and mainly > uses

[sage-devel] Ask about the SageMath codebase using ChatGPT

y. Best, Naren Co-Founder & CTO at Wolfia (YC S22) (314) 562-8039 | LinkedIn | Twitter -- Best Regards, William Stein CEO, SageMath, Inc. https://cocalc.com -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

Re: [sage-devel] Question about reading Sage documentation

Hi, Related Question: Is anybody interested in making it so https://doc.sagemath.org/ hosts many different versions of the Sage documentation instead of just the latest? I only looked into this for a second, but readthedocs.io often has many versions of docs for projects. Also, I always appreci

Re: [sage-devel] Voting: Block-scoped optional tag and the keyword

I vote for (A) On Wed, Jun 28, 2023 at 7:40 PM Kwankyu Lee wrote: > Hi, > > We spent six days for the preliminary discussion in the sage-devel thread > > https://groups.google.com/g/sage-devel/c/OUnoroIf0qc > > about choosing the keyword triggering block-scoped optional tag needed in > > https:/

Re: [sage-devel] Modularization project: I. The goals

On Fri, Jun 23, 2023 at 1:02 PM Michael Orlitzky wrote: > The second issue is that WebAssembly doesn't actually solve the > problems we have, By "the problem we have" I guess maybe you mean "Sage is a lot of work to maintain".The fundamental and massive problem that I think SageMath has is

Re: [sage-devel] Modularization project: I. The goals

On Thu, Jun 22, 2023 at 2:15 PM Michael Orlitzky wrote: > On Thu, 2023-06-22 at 13:56 -0700, William Stein wrote: > > > > (5) provide a WebAssembly option > > > > WebAssembly is typically about half the speed as native code (at best), > but > > it is high

Re: [sage-devel] Modularization project: I. The goals

On Thu, Jun 22, 2023 at 1:44 PM Matthias Koeppe wrote: > > On Thursday, June 22, 2023 at 12:49:29 PM UTC-7 Francesco Biscani wrote: > > On Fri, 9 Jun 2023 at 02:02, Matthias Koeppe wrote: > > building binary wheels to be distributed on PyPI (in addition to the source distributions) will be one of

Re: [sage-devel] Modularization project: I. The goals

lways be GPL'd), but it is something we have to be realistic about. > Perhaps this is the question that I am looking for an answer for, "What is > Sage (after modularization)?" Sage would be part of the Python ecosystem. > > Best, > Travis > > > On

Re: [sage-devel] Re: Modularation doctests

emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/80a6ba58-17e8-4a99-950a-3bfb5e0b24fen%40googlegroups.com > <https://groups.google.com/d/msgid/sage-devel/80a6ba58-17e8-4a

Re: [sage-devel] Modularization project: I. The goals

Hi Sage Devs, As further motivation for this discussion of "Modularization project: I. The goals", here is a quote from a discussion just now (with permission) from Eric Deeds, who is the vice chair for Life Sciences Math Courses and Professor of Integrative Biology and Physiology at UCLA: "I thi

Re: [sage-devel] Re: Why matrix powers are slower over Integers(p) than in ZZ?

On Wed, Jun 14, 2023 at 10:15 AM David Roe wrote: > > The problem is that Sage doesn't have a specialized type for integers mod N: > sage: type(M3) > More precisely, Sage doesn't have a specialized type for matrices over integers mod N, for N *large*. For smaller N it does, e.g., sage: p=next

Re: [sage-devel] Modularization project: I. The goals

On Sun, Jun 11, 2023 at 6:53 PM Matthias Koeppe wrote: > On Sunday, June 11, 2023 at 6:20:03 PM UTC-7 Travis Scrimshaw wrote: > > My understanding of William's goal (please correct me if I am wrong) was > to put everything together so nobody was trying to build a better wheel. To > me, by splitti

Re: [sage-devel] Develop Sage inside GitHub Codespaces and/or other "cloud" options?

475ea1-a782-4c54-a3dc-a8d1dacc8b53n%40googlegroups.com. >> >> > -- > 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+u

Re: [sage-devel] Re: ping - please cast you vote: VOTE: Follow NEP 29: Recommended Python version

9d557-fd7d-4c6a-8644-3ee96966b8fan%40googlegroups.com > <https://groups.google.com/d/msgid/sage-devel/d459d557-fd7d-4c6a-8644-3ee96966b8fan%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- -- William Stein -- You received this message because you are subscribed t

Re: [sage-devel] ping - please cast you vote: VOTE: Follow NEP 29: Recommended Python version

On Tue, May 30, 2023 at 2:15 AM Dima Pasechnik wrote: > > So far we only had very few votes cast. You might want to consider structuring the voting process more. For example, David Roe did a great job with this for the "move sage to github" vote, including a clear deadline, a thread where no dis

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 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: What was/is/will be the purpose of maintaining the Sage distribution?

On Thu, Apr 27, 2023 at 1:21 PM Matthias Koeppe wrote: > > On Thursday, April 27, 2023 at 5:49:50 AM UTC-7 William Stein wrote: > > To what extent does or could Conda with a little more work solve most > of these problems? [...] > I also think this section > https://doc

Re: [sage-devel] Re: What was/is/will be the purpose of maintaining the Sage distribution?

special in that it has tons of dependencies. > > As usual, the biggest hurdle to making things work more seamlessly is > manpower. > Most of the niche packages that sage depends on are maintained by me and > Julian and improvements > to supporting conda in the sage build system

Re: [sage-devel] Re: What was/is/will be the purpose of maintaining the Sage distribution?

Hi, To what extent does or could Conda with a little more work solve most of these problems? There are some notes below from me poking around, and I'm very optimistic. I looked at https://doc.sagemath.org/html/en/installation/conda.html and I would love some further discussion of that and whe

Re: [sage-devel] Re: [sage-release] Sage 10.0.rc0 released

eiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/3c05b1b8-f8e3-4fb1-b39e-f296e5efd40bn%40googlegroups.com > <https://groups.google.com/d/msgid/sage-devel/3c05b1b8-f

Re: [sage-devel] Re: [sage-release] Sage 10.0.rc0 released

On Wed, Apr 26, 2023 at 12:27 PM David Roe wrote: > > I'm sorry to have prompted another flame war, but please keep the tone polite > Dima and Matthias. I know that you're both frustrated at this issue being > unresolved, but it's not appropriate to have a fight like this that goes to > 2570 d

Re: [sage-devel] Re: [sage-release] Sage 10.0.rc0 released

Hi Everybody, Just a reminder of https://github.com/sagemath/sage/blob/develop/CODE_OF_CONDUCT.md In particular, 1. Be friendly and patient. 2. Be welcoming. 3. Be considerate. 4. Be respectful and polite. As a community, we've agreed that these are very reasonable ways to conduct ourselves on

Re: [sage-devel] Re: [sage-release] Sage 10.0.rc0 released

On Wed, Apr 26, 2023 at 10:40 AM Dima Pasechnik wrote: > > For a long time it was very important for getting a functional Sage on > > MacOS; is that no longer the case? > Sorry, I don't understand. > > Noone I know builds Python (the only package that needs openssl) from source. > For a long tim

Re: [sage-devel] Re: Why SR('expression') fail on some but not others?

I put a few remarks related to this in a notebook: https://cocalc.com/wstein/support/SR-and-strings Basically, converting to from strings via str hardly works anywhere in Sage and that is by design, following the lead of Magma instead of Pari. Instead Pickle is the thing that mostly works for th

Re: Re: [sage-devel] ChatGPT is an expert in SageMath too

Hi, There's is a discussion right now on HN about LLM's trained on code https://news.ycombinator.com/item?id=35657982 One of the comments https://news.ycombinator.com/item?id=35658118 points out that most of the non-GPL super permissive licenses require explicit attribution when creating derived

Re: [sage-devel] ChatGPT is an expert in SageMath too

Hi, I don't know whether or not ChatGPT is trained on the source code of SageMath, but one of the biggest publicly available training sets of code is described here: https://arxiv.org/abs/2211.15533 In that training set, they explicitly remove any GPL'd code (e.g., SageMath): "Permissive license

Re: [sage-devel] RealField isn't doing it right

On Tue, Apr 18, 2023 at 7:35 PM aw wrote: > [...] You and your people have a *very strong* tendency to nitpick details > instead of staying focused on the big picture. You're right, respecting details is indeed a very strong characteristic of professional mathematicians. -- William (http://wst

Re: [sage-devel] RealField isn't doing it right

On Tue, Apr 18, 2023 at 5:15 PM aw wrote: > In high-precision environments like RealField(1000), Sage should *definitely* > use the math semantics, because physics people, or engineers, or any other > applied type folks, have zero use for 1000 bits of precision in anything that > they do. Sear

Re: [sage-devel] RealField isn't doing it right

On Mon, Apr 17, 2023 at 9:11 PM Nils Bruin wrote: > > It's certainly reasonable to not call a floating point field "RealField". > C and python don't even do that: they call such elements floats. I'm less > sure whether such a RealFloats field should be any less prominent than it > is now. Plus th

Re: [sage-devel] modular form basis

On Mon, Apr 17, 2023 at 9:13 AM Ralf Hemmecke wrote: > > Hello, > > is there any particular reason why the term 12/5*q is not subtracted > away by the first basis element? The answer is that M_2(Gamma0(11)) is represented internally as the direct sum of the cuspidal and eisenstein subspaces. In p

Re: [sage-devel] RealField isn't doing it right

On Sat, Apr 15, 2023 at 4:25 PM Michael Orlitzky wrote: > > On Sat, 2023-04-15 at 18:20 -0400, David Roe wrote: > > I agree with William that you should refrain from insulting the Sage > > developers, especially when the underlying problem comes from your > > misunderstanding of how floating point

Re: [sage-devel] RealField isn't doing it right

https://github.com/sagemath/sage/blob/develop/CODE_OF_CONDUCT.md On Sat, Apr 15, 2023 at 2:39 PM aw wrote: > > Guys, this is serious. Any dev who starts reading this, give it a hard look, > ok? > > Below I give some examples where Sage give the wrong answer, with no error > message or any indic

[sage-devel] Sage developer's guide

om Trac to GitHub for the preliminary version of the workflow." It seems like that banne could be updated a bit, now that it is April. I do realize that there's still a lot being hashed out about the exact workflow... William [1] https://doc.sagemath.org/html/en/developer/index.html -- B

Re: [sage-devel] Re: where is rpy2

+1 On Sat, Mar 25, 2023 at 1:40 PM Matthias Koeppe wrote: > > On Saturday, March 25, 2023 at 12:52:00 PM UTC-7 Dima Pasechnik wrote: > > I propose to introduce the notion of semistandard package. > > > "Semistandard" sounds good to me. > > We have a few more packages that are of this type: > - s

Re: [sage-devel] Re: where is rpy2

On Sat, Mar 25, 2023 at 12:13 PM Dima Pasechnik wrote: > > > > On Sat, 25 Mar 2023, 18:57 Matthias Koeppe, wrote: >> >> On Saturday, March 25, 2023 at 9:29:32 AM UTC-7 William Stein wrote: >> >> It seems to me that these days there are three >&g

Re: [sage-devel] Re: where is rpy2

On Sat, Mar 25, 2023 at 11:53 AM Matthias Koeppe wrote: > > rpy2 is built by default when a suitable system R is detected. Thanks. This is exactly my understanding. The Sage docs https://doc.sagemath.org/html/en/developer/packaging.html define standard, optional and experimental packages. The d

[sage-devel] where is rpy2

Hi, According to https://doc.sagemath.org/html/en/reference/spkg/rpy2.html#spkg-rpy2 the rpy2 package is a "standard package". However, I just checked multiple builds in various places of sage-9.8 and also the latest master branch, and rpy2 is not installed. I can see why rpy2 isn't installed.

Re: [sage-devel] Github Discussions

23 at 10:10 AM Oscar Benjamin wrote: > > On Wed, 8 Feb 2023 at 16:47, William Stein wrote: > > > > Hi Sage Devs, > > > > Any thoughts about enabling "Github Discussions" for SageMath on > > Github now? > > I just want to share my experience of this

[sage-devel] Github Discussions

Hi Sage Devs, Any thoughts about enabling "Github Discussions" for SageMath on Github now? The tab is already visible, but somebody has to I think fully enable it and do some configuration. https://github.com/sagemath/sage/discussions/landing This can be used much like ask.sagemath.org or sage-

Re: [sage-devel] Re: Democratic issue: rushing decisions

On Thu, Oct 6, 2022 at 8:45 AM John H Palmieri wrote: > Hi William, > There is nothing in our department's bylaws to provide for a delay of voting, > but we have a chair and we have an executive committee, and the hope is that > they care not only about the particular issue at hand, but also abo

Re: [sage-devel] Re: Democratic issue: rushing decisions

On Wed, Oct 5, 2022 at 8:09 PM John H Palmieri wrote: > > The main response I saw to the requests for a slower process was from David > Roe, saying, "Finally, since we're just voting on trac vs github I don't > think there's a need to draw out the discussion until October 1, and several > peopl

Re: [sage-devel] Democratic issue: rushing decisions

> several developers asked for delays The only governance mechanism we have for decision making in the Sage project currently is a vote of the entire dev community. Thus there is no way to consider your request to delay voting aside from having even more voting. -- William On Wed, Oct 5, 202

Re: [sage-devel] Re: Invitation: Weekly 30-minute Sage developer calls on Jitsi

; To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/CAAWYfq2Vm4yakjdu8JQ3WF-Y0NK7s-B%3Dwug-b%2B5qKDOMw2yRvg%40mail.gmail.com &

Re: [sage-devel] DISCUSS: move Sage development to Github

On Sat, Sep 24, 2022 at 9:15 AM Matthias Koeppe wrote: > > On Saturday, September 24, 2022 at 4:57:36 AM UTC-7 kcrisman wrote: >>> >>> On another note, I realize that the comment I made 6 years ago after >>> Volker's comment is still relevant: >> >> "There's also the non-trivial (though not block

Re: [sage-devel] Re: is it intentional that prod does not stop when it hits 0?

Note also that prod(range(1,n)) does *NOT* just multiple 1 times 2 times 3 in order. Instead, it uses a tree approach so that the multiplications involve objects with more balanced sizes, which is much faster, e.g., for large integers multiplyling n*m with n and m having similar sizes can overall

Re: [sage-devel] VOTE: move Sage development to Github

+1 for Github On Wed, Sep 21, 2022 at 10:23 AM David Roe wrote: > > Dear Sage developers, > Following extensive discussion, both recently (prompted by issues upgrading > the trac server) and over the last decade, we are calling a vote on switching > Sage development from Trac to Github. We've

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

contributors (quite a few by the same > person, but different emails etc), > see attachment > > > > I'm sure we could get a full list of author names from git. > > David > > > > On Tue, Sep 20, 2022 at 12:35 PM Dima Pasechnik wrote: > >> > >>

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

On Tue, Sep 20, 2022 at 4:09 AM Dima Pasechnik wrote: > > On Tue, Sep 20, 2022 at 11:51 AM kcrisman wrote: > > > > > >>> "Subscribed to sage-devel" might not be a good criteria. For example, > >>> Harald Schilly has been the webmaster of Sage since 2007 and likely > >>> cares about this switch si

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

attempting to > summarize arguments in favor of each system, and this thread can serve as a > space for people to make clear their own reasoning for favoring one option > over the other. This discussion has gotten heated at times, so remember to > be considerate, respectful and polit

Re: [sage-devel] Re: Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

Here is a 3-minute section of a PyCon 2022 keynote by the steering council discussing migration of CPython to GitHub: https://youtu.be/m2R5shF1pLc?t=535 In particular, they talk about how much effort went into the migration, and just how difficult it was, and how GitHub was directly involved with

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

On Sun, Sep 18, 2022 at 10:27 AM Matthias Koeppe wrote: > > On Sunday, September 18, 2022 at 10:14:26 AM UTC-7 Nils Bruin wrote: >> >> On Saturday, 17 September 2022 at 17:55:10 UTC-7 Matthias Koeppe wrote: >>> >>> >>> The conversion of the Trac tickets to GitHub Issues/PRs only works in one >>>

Re: [sage-devel] Re: incremental migration to github? [prompted by FUNDING issues!!!] + general flakiness of trac

On Fri, Sep 16, 2022 at 12:34 PM Dima Pasechnik wrote: >> - Some people with strong opinions said that they are not ready to formulate >> their views. >> >> My impression is that trac is now doing okay, > > > Note that trac's bus factor is down to 1/3. It took efforts of Frederick, > Jan, and me

Re: [sage-devel] Re: On changing Bernoulli(1) to +½

vel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/155dc41c-6d30-4792-923f-2ff85d831de7n%40googlegroups.com > <https://groups.google.com/d/msgid/sage-devel/155dc41c-6d30-4792-923f-2ff85d831de7n%40googlegroups.com?utm_m

Re: [sage-devel] sage zoom meeting reminder

We took quick notes from the discussion during the short meeting here - https://cocalc.com/wstein/sagedev/2022-09-15 On Thu, Sep 15, 2022 at 8:19 AM William Stein wrote: > > I've also created an agenda file here: > > https://cocalc.com/wstein/sagedev/2022-09-15 > >

Re: [sage-devel] sage zoom meeting reminder

please create a meeting and > post the details here? > > Matthias > > On Thursday, September 15, 2022 at 8:16:42 AM UTC-7 Dima Pasechnik wrote: >> >> On Thu, Sep 15, 2022 at 3:54 PM William Stein wrote: >> > >> > Reminder -- that 30 minute Sage zoom mee

Re: [sage-devel] sage zoom meeting reminder

Matthias just wrote that he is having technical troubles with zoom. Here's where we will have the meeting instead: https://meet.jit.si/d8a744b413e339d95fba907b81fb249609520161 On Thu, Sep 15, 2022 at 8:16 AM Dima Pasechnik wrote: > > On Thu, Sep 15, 2022 at 3:54 PM William S

  1   2   3   4   5   6   7   8   9   10   >