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

Dima's suggestion is appealing, and somewhat along those lines, I like the idea changing Sage to use some standard documentation style (https://github.com/sagemath/sage/issues/31044). If the program provides a technical writer, though, those may not be suitable goals. A quick glance at least

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

I think the main question is who is willing to take the lead on writing and submitting applications (before April 2). I don't have enough time in the next three weeks to do any writing, but I am willing to help brainstorm what form the proposal(s) should take and help edit proposals if someone

Re: [sage-devel] Re: conda sage

Minor correction -- they say "Given its wide usage, there are no plans to deprecate Mambaforge." So Mambaforge isn't deprecated as I incorrectly wrote. It's just "discouraged". I'm sorry for the noise, but the *conda* packaging ecosystem makes me dizzy... On Sun, Mar 10, 2024 at 5:31 PM

Re: [sage-devel] Re: conda sage

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 people should install Miniforge, i.e., "(Discouraged as of September 2023)". We

Re: [sage-devel] Re: conda sage

Hi, So I was using MicroMamba, whereas that page says Sage only supports Mambaforge, Miniforge, Miniconda or Anaconda.I tried with Mambaforge (as recommended there) and everything works perfectly, with sage-10.2 being available, and nicely integrated with the conda ecosystem, and also it's

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

Yes, we could prepare several proposals for separate projects. One can see in the lists of past funded projects that some organizations have received funding for two simultaneous projects. On Sunday, March 10, 2024 at 8:38:13 AM UTC-7 John Cremona wrote: > Should there not be separate projects

Re: [sage-devel] Re: conda sage

I suppose you can try instead using the switch "--rc-file" with the rc-file provided by Sage in https://github.com/sagemath/sage/blob/develop/condarc.yml On Sunday, March 10, 2024 at 1:48:15 PM UTC-7 William Stein wrote: > On Sun, Mar 10, 2024 at 1:39 PM Matthias Koeppe > wrote: > >>

Re: [sage-devel] Re: conda sage

On Sun, Mar 10, 2024 at 1:39 PM Matthias Koeppe wrote: > William, do the instructions in our Installation Guide work for you? > > https://deploy-livedoc--sagemath.netlify.app/html/en/installation/conda#install-from-conda-forge > > > Note in particular this step: "Change channel priority to

[sage-devel] Re: conda sage

William, do the instructions in our Installation Guide work for you? https://deploy-livedoc--sagemath.netlify.app/html/en/installation/conda#install-from-conda-forge Note in particular this step: "Change channel priority to strict: conda config --set channel_priority strict" On Sunday,

[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

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

On Sun, Mar 10, 2024 at 1:44 PM seb@gmail.com wrote: > Personally I don't mind if a maintainer would correct my typos in the PR > description (or something else according to Volker's white list). However, > since this is a privileged action and we cannot be sure that everyone feels > this

Re: [sage-devel] VOTE: disputed PRs

+1 David Lowry-Duda schrieb am Samstag, 9. März 2024 um 00:18:12 UTC+1: > +1 > > - DLD > > On 03:23 Mon 04 Mar 2024, David Roe wrote: > >With no further discussion on this thread > >, I'm calling a > vote > >on a new process for resolving

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

Personally I don't mind if a maintainer would correct my typos in the PR description (or something else according to Volker's white list). However, since this is a privileged action and we cannot be sure that everyone feels this way, I think this point should be addressed generally. Perhaps the

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

+1 Eric Gourgoulhon schrieb am Sonntag, 10. März 2024 um 16:58:42 UTC+1: > +1 > > Eric. > > -- 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

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

Hi, I also strongly support this initiative for Sage to join NumFocus at this point in time. Regarding Cython, I made up the name in maybe 2008, and started it as a project by combining "Pyrex" that Greg Ewing worked on periodically, my own fork of Pyrex that had features I added that were

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

+1 Eric. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit

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] Google Season of Docs – org application deadline April 2

Not sure whether switching Sage to standard Sphinx/Python docbuilding tools falls within the remit of the Season of Docs, but it's surely a worthwhile project - in particular if we can get funds for it. On Sun, Mar 10, 2024 at 3:03 PM David Roe wrote: > I think this would be good for Sage. I

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

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

Should there not be separate projects for documenting (1) building and installing Sage; (2) using Sage (perhaps with some subject-specific tutorials, some of which exist but might be worth updating) and (3) documenting individual Sage functions and methods. These require different expertise, for

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] Heun function support

On 10 March 2024 05:24:31 GMT, Steve Dodge wrote: >Hello, I was curious to know if there are any plans to include support for >Heun >functions in Sage, or if anyone knows of a >reliable and well-documented implementation of them elsewhere.

Re: [sage-devel] weirdest bug ever

Oh no! Thank you! On Saturday 9 March 2024 at 23:24:20 UTC+1 Gareth Ma wrote: > You typed `mononomials` instead of `monomials`. That's a nono. > > > On 09/03/2024 22:22, 'Martin R' via sage-devel wrote: > > If I store this in a file "bug.sage" I can do: > > sage: load('/home/martin/bug.sage') >