date:20240322




On 22 March 2024 23:01:47 GMT, Matthias Koeppe  wrote:
>On Friday, March 22, 2024 at 3:31:07 PM UTC-7 Dima Pasechnik wrote:
>
>They are not really "tested" - just as much of the rest of Jupiter stuff is 
>not tested in our CI.
>
>(installability - yes, 
>
> 
>The installability of it is exactly what was broken in Sage 10.2. 
>We test automatically so that we do not have to wait for users' bug reports.
>
>in a strange non-standard environment,
>
>
>The installability of the package is tested in the relevant environment, 
>namely the Sage venv.
>
>I need to ask you to drop these mischaracterizations of the Sage venv as 
>something "strange" or "non-standard". There's no technical basis for this, 


Of course it is strange and non-standard.
A custom venv, non-standard commands to launch things, pinned to seemingly 
random values versions of packages, etc.

>and repeating it is harmful to the project. 
>https://groups.google.com/g/sage-devel/c/OeN8o14s6Jc
>
>but whether the notebooks actually work, who knows)
>
>
>We know because the reviewer of the upgrade 
>ticket https://github.com/sagemath/sage/pull/37478 tested it. 

you claimed they are tested by CI, not by humans.


>

-- 
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 
https://groups.google.com/d/msgid/sage-devel/61B136FB-2D22-4523-A59B-07ED765DF12B%40gmail.com.

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

On Friday, March 22, 2024 at 3:31:07 PM UTC-7 Dima Pasechnik wrote:

They are not really "tested" - just as much of the rest of Jupiter stuff is 
not tested in our CI.

(installability - yes, 

 
The installability of it is exactly what was broken in Sage 10.2. 
We test automatically so that we do not have to wait for users' bug reports.

in a strange non-standard environment,


The installability of the package is tested in the relevant environment, 
namely the Sage venv.

I need to ask you to drop these mischaracterizations of the Sage venv as 
something "strange" or "non-standard". There's no technical basis for this, 
and repeating it is harmful to the project. 
https://groups.google.com/g/sage-devel/c/OeN8o14s6Jc

but whether the notebooks actually work, who knows)


We know because the reviewer of the upgrade 
ticket https://github.com/sagemath/sage/pull/37478 tested it. 

-- 
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 
https://groups.google.com/d/msgid/sage-devel/40a46715-3152-48b7-8810-e4049e5f3c2fn%40googlegroups.com.

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

I don't think that one would look for e.g. a Jupyter interface to Pari-GP in 
the catalog of sage spkgs.

The natural place is Pari-GP website.

They are not really "tested" - just as much of the rest of Jupiter stuff is not 
tested in our CI.
(installability - yes, in a strange non-standard environment, but whether the 
notebooks actually work, who knows)

pytest has a special plugin, nbmake, to test notebook, and testing notebook 
kernels/clients ought to involve running actual notebooks on them.

Jupyter interface for Singular seems to be an old beta, and it's just funny to 
try to offer anything for R, given how big R is compared to Sage.

Let's drop them all from Sage distribution.

On 22 March 2024 21:40:24 GMT, Matthias Koeppe  wrote:
>On Friday, March 22, 2024 at 12:02:30 PM UTC-7 Nils Bruin wrote:
>
>It looks to me like a project that can easily not be offered as an spkg, 
>with minimal effect, but I might be overlooking something. 
>
>
>What you might be overlooking is that 
>- our catalog of SPKGs is a useful curation that serves our users;
>- our workflows on GH Actions automatically test the packages in our 
>catalog on every release.
>
>-- 
>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 
>https://groups.google.com/d/msgid/sage-devel/106f3ff1-42c1-469b-a536-7de0857c0080n%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CFECCC91-D26A-483F-A4FC-4AB4BBD298A5%40gmail.com.

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

On Friday, March 22, 2024 at 12:02:30 PM UTC-7 Nils Bruin wrote:

It looks to me like a project that can easily not be offered as an spkg, 
with minimal effect, but I might be overlooking something. 


What you might be overlooking is that 
- our catalog of SPKGs is a useful curation that serves our users;
- our workflows on GH Actions automatically test the packages in our 
catalog on every release.

-- 
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 
https://groups.google.com/d/msgid/sage-devel/106f3ff1-42c1-469b-a536-7de0857c0080n%40googlegroups.com.

Re: [sage-devel] pari-jupyter 1.4.3 release candidate




On 22 March 2024 19:02:30 GMT, Nils Bruin  wrote:
>On Friday 22 March 2024 at 11:22:12 UTC-7 Matthias Koeppe wrote:
>
>10 days ago, the previous maintainer, Vincent Delecroix, announced that he 
>steps down from maintaining it. 
>https://groups.google.com/g/sage-devel/c/fy1ei6bLtmc
>I did some emergency maintenance and on that occasion I added the 
>"Maintainers" field in the metadata. Nobody specifically committed to 
>maintaining it or made a plan, as far as I know.
>
>
>Thanks for that. Obviously, when a maintainer steps down, some follow-up 
>should happen and by the location of the repository, the sagemath community 
>inherits the project in this case by default.
>
>It looks to me like a project that can easily not be offered as an spkg, 
>with minimal effect, but I might be overlooking something. So removing the 
>spkg could make sense.

There are also similarly disjoint from Sage packages r-jupyter, 
singular-jupyter, see


they can similarly be removed from Sage.
(but mentioned in the docs)


>
>Judging from the thread here:
>
>https://pari.math.u-bordeaux.fr/archives/pari-dev-2305/msg2.html
>
>this kernel is very much the basis for whatever Bill is considering. 
>Further down the thread, there is also a reference to Edgar Costa's kernel:
>
> https://github.com/edgarcosta/gp_kernel
>
>it looks like the discussion there may lead to a new home for the project 
>eventually (or another project to take its place).
>

-- 
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 
https://groups.google.com/d/msgid/sage-devel/B3CC456D-14F1-454B-A594-84CE4877765E%40gmail.com.

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

2024-03-22 Thread 'Gonzalo Tornaría' via sage-devel

Thanks David,

It would be interesting to add nominations that were banned into the
analysis. For all we know, somebody could have received 16/17 votes if they
were in the ballot, but a single negative vote was enough to prevent that.

Could you add anonymized information about nominations that didn't make it
into the ballot, and about the vetos that you received?

Best,
Gonzalo

On Wednesday, March 20, 2024 at 1:58:48 PM UTC-3 David Roe wrote:

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=3 candidates out of 6, say, $a,b,c,d,e,f$, and
out of N=19 people, 10 vote for $a,b,c$, and 9 - for $d,e,f$, then, with
approval voting, $a,b,c$ get elected (as $a,b,c$, get 10 votes each, more
than $d,e,f$), and almost half the voters, 9 out of 10, get no
representation of their views.
This is obviously bad - in such a case a fair outcome would be something
like $a,b,d$. Here "fair" has to be quantified, of course.
I've posted some details (and pointed at some solutions) on this here:
https://github.com/sagemath/sage/pull/37501#issuecomment-2004121053

It would be interesting to get the anonymised returned ballots and see if
we did well on this occasion.
As well, adjustments ought to be made along the lines outlined above.

The committee has agreed to release anonymized voting records, since the
benefit gained for picking a better system for future votes outweighs the
privacy risk (we've anonymized both voters and candidates). As I explained
here ,
if we had stuck with 5 people on the committee then different system would
have had different results, but after extending to 6 based on the
approval-voting tie there was broad agreement: Approval Voting,
Proportional Approval Voting, Phragmén's sequential rule, Maximin Support
and Equal Shares all selected the current committee; only Minimax approval
voting had a different result.

The anonymized votes are here
,

in case anyone wants to do further analysis.
David

--
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
https://groups.google.com/d/msgid/sage-devel/1518a6dc-01e1-444e-87f7-95a6b244f106n%40googlegroups.com.

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

2024-03-22 Thread Nils Bruin

On Friday 22 March 2024 at 11:22:12 UTC-7 Matthias Koeppe wrote:

10 days ago, the previous maintainer, Vincent Delecroix, announced that he
steps down from maintaining it.
https://groups.google.com/g/sage-devel/c/fy1ei6bLtmc
I did some emergency maintenance and on that occasion I added the
"Maintainers" field in the metadata. Nobody specifically committed to
maintaining it or made a plan, as far as I know.

Thanks for that. Obviously, when a maintainer steps down, some follow-up
should happen and by the location of the repository, the sagemath community
inherits the project in this case by default.

It looks to me like a project that can easily not be offered as an spkg,
with minimal effect, but I might be overlooking something. So removing the
spkg could make sense.

Judging from the thread here:

https://pari.math.u-bordeaux.fr/archives/pari-dev-2305/msg2.html

this kernel is very much the basis for whatever Bill is considering.
Further down the thread, there is also a reference to Edgar Costa's kernel:

https://github.com/edgarcosta/gp_kernel

it looks like the discussion there may lead to a new home for the project
eventually (or another project to take its place).

--
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
https://groups.google.com/d/msgid/sage-devel/a0c2c036-f880-4606-9d39-2386e184ae23n%40googlegroups.com.

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

10 days ago, the previous maintainer, Vincent Delecroix, announced that he 
steps down from maintaining it. 
https://groups.google.com/g/sage-devel/c/fy1ei6bLtmc
I did some emergency maintenance and on that occasion I added the 
"Maintainers" field in the metadata. Nobody specifically committed to 
maintaining it or made a plan, as far as I know.

On Friday, March 22, 2024 at 10:52:16 AM UTC-7 Marc Culler wrote:

> By looking at the pari-jupyter page on PYPI I learned that it was written 
> by Jeroen Demeyer and is maintained by the SageMath Developers.  So I guess 
> I don't understand what the relation is between SageMath and pari-jupyter.  
> Will pari-jupyter be competing with the kernel that Bill Allombert is 
> writing?  Is there a reason why he is writing a kernel when one already 
> exists?  Obviously I have no idea what I am talking about and am publicly 
> revealing my ignorance.
>
> - Marc
>
>
> On Friday, March 22, 2024 at 12:29:56 PM UTC-5 Marc Culler wrote:
>
>> I wasn't advocating anything like that.  Certainly I don't think that 
>> pari-jupyter should be "killed".  I am assuming that pari-jupyter is or 
>> will be a package that can be installed with pip.  And I am also assuming 
>> that it has no direct interaction with Sage.  Are those assumptions wrong?  
>> If not, what benefit does the pari-jupyter project get from having it 
>> available as a sage spkg?
>>
>> A question of more relevance to me is: do I need to add pari-jupyter to 
>> the Sage_macOS binary package, even though it could be installed separately 
>> by just running pip?  (We try to add all optional packages the we can 
>> build.). If installing pari-jupyter creates a kernel specification 
>> directory in /usr/local/share (as we do for the Sage kernel), then it will 
>> appear as an available kernel when jupyter is launched from the SageMath 
>> app, whether or not the location of the kernel is inside the app bundle.  
>> How does it improve our user's experience to have the package installed 
>> inside of the app bundle, as opposed to in the user's Library/Python 
>> directory or inside the python.org framework?  While this question is 
>> specific to me, I think the same question applies to SageMath.
>>
>> - Marc
>>
>>
>> On Friday, March 22, 2024 at 12:13:34 PM UTC-5 Matthias Koeppe wrote:
>>
>>> Let me just point out that the idea that "grant has ended, so we can 
>>> kill its deliverables" is fundamentally flawed, and certainly is not and 
>>> cannot be the position of our project.
>>>
>>> Infrastructure grants are exactly set up for their longer-term and 
>>> broader impacts. 
>>>
>>> Matthias
>>>
>>> On Friday, March 22, 2024 at 5:58:47 AM UTC-7 Dima Pasechnik wrote:
>>>
 I don't see any reason for pari-jupyter being a sage package. It has 
 nothing in common with sagelib, it's a standalone jupyter kernel for 
 Pari-GP.
 It has ended up in sage in OpenDreamKit times, to make granting agency 
 happy.


 On Thu, Mar 21, 2024 at 8:42 AM Edgar Costa  
 wrote:

> Bill Allombert has been working on a kernel via xeus:
> https://pari.math.u-bordeaux.fr/git/xeus-gp.git/
> Which addresses many of the issues with the current one.
> While we for its first stable release, I recommend mine: 
> https://github.com/edgarcosta/gp_kernel/
> where I have addressed many of the issues, by going through the route 
> that every cell is a temporary file, which is loaded in gp.
>
>
> On Thu, Mar 21, 2024 at 4:29 AM Matthias Koeppe  
> wrote:
>
>> - https://pypi.org/project/pari-jupyter/1.4.3rc1/
>> - I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just 
>> point to the main sagemath repository
>> - using WIP sage-project-cookiecutter to simplify maintenance 
>> https://github.com/sagemath/sage/pull/37541
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/e822f186-6504-4516-9940-d03398f270b9n%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+...@googlegroups.com.
>
 To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x5FYigLmaKMc0wodYJB9BUqsdpyuy63RrxXoTcv%2BQKTJw%40mail.gmail.com
>  
>

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

By looking at the pari-jupyter page on PYPI I learned that it was written 
by Jeroen Demeyer and is maintained by the SageMath Developers.  So I guess 
I don't understand what the relation is between SageMath and pari-jupyter.  
Will pari-jupyter be competing with the kernel that Bill Allombert is 
writing?  Is there a reason why he is writing a kernel when one already 
exists?  Obviously I have no idea what I am talking about and am publicly 
revealing my ignorance.

- Marc


On Friday, March 22, 2024 at 12:29:56 PM UTC-5 Marc Culler wrote:

> I wasn't advocating anything like that.  Certainly I don't think that 
> pari-jupyter should be "killed".  I am assuming that pari-jupyter is or 
> will be a package that can be installed with pip.  And I am also assuming 
> that it has no direct interaction with Sage.  Are those assumptions wrong?  
> If not, what benefit does the pari-jupyter project get from having it 
> available as a sage spkg?
>
> A question of more relevance to me is: do I need to add pari-jupyter to 
> the Sage_macOS binary package, even though it could be installed separately 
> by just running pip?  (We try to add all optional packages the we can 
> build.). If installing pari-jupyter creates a kernel specification 
> directory in /usr/local/share (as we do for the Sage kernel), then it will 
> appear as an available kernel when jupyter is launched from the SageMath 
> app, whether or not the location of the kernel is inside the app bundle.  
> How does it improve our user's experience to have the package installed 
> inside of the app bundle, as opposed to in the user's Library/Python 
> directory or inside the python.org framework?  While this question is 
> specific to me, I think the same question applies to SageMath.
>
> - Marc
>
>
> On Friday, March 22, 2024 at 12:13:34 PM UTC-5 Matthias Koeppe wrote:
>
>> Let me just point out that the idea that "grant has ended, so we can kill 
>> its deliverables" is fundamentally flawed, and certainly is not and cannot 
>> be the position of our project.
>>
>> Infrastructure grants are exactly set up for their longer-term and 
>> broader impacts. 
>>
>> Matthias
>>
>> On Friday, March 22, 2024 at 5:58:47 AM UTC-7 Dima Pasechnik wrote:
>>
>>> I don't see any reason for pari-jupyter being a sage package. It has 
>>> nothing in common with sagelib, it's a standalone jupyter kernel for 
>>> Pari-GP.
>>> It has ended up in sage in OpenDreamKit times, to make granting agency 
>>> happy.
>>>
>>>
>>> On Thu, Mar 21, 2024 at 8:42 AM Edgar Costa  
>>> wrote:
>>>
 Bill Allombert has been working on a kernel via xeus:
 https://pari.math.u-bordeaux.fr/git/xeus-gp.git/
 Which addresses many of the issues with the current one.
 While we for its first stable release, I recommend mine: 
 https://github.com/edgarcosta/gp_kernel/
 where I have addressed many of the issues, by going through the route 
 that every cell is a temporary file, which is loaded in gp.


 On Thu, Mar 21, 2024 at 4:29 AM Matthias Koeppe  
 wrote:

> - https://pypi.org/project/pari-jupyter/1.4.3rc1/
> - I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just 
> point to the main sagemath repository
> - using WIP sage-project-cookiecutter to simplify maintenance 
> https://github.com/sagemath/sage/pull/37541
>
> -- 
> 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+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-devel/e822f186-6504-4516-9940-d03398f270b9n%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+...@googlegroups.com.

>>> To view this discussion on the web visit 
 https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x5FYigLmaKMc0wodYJB9BUqsdpyuy63RrxXoTcv%2BQKTJw%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c319f93a-7d6a-4876-9066-b1566a9a6c95n%40googlegroups.com.

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

2024-03-22 Thread seb....@gmail.com

+1

Marc Culler schrieb am Freitag, 22. März 2024 um 15:55:20 UTC+1:

> +1
>
> On Thursday, March 21, 2024 at 11:51:40 AM UTC-5 John H Palmieri wrote:
>
>> Dear Sage community,
>>
>> As announced at 
>> https://groups.google.com/g/sage-devel/c/Xf6dbPLmKPY/m/p88auKlBAwAJ, I 
>> propose some changes to the Code of Conduct. Those changes have been 
>> discussed and modified based on feedback from several developers: visit 
>> https://github.com/sagemath/sage/pull/37501 for details. Those changes 
>> are now ready for a vote here on sage-devel. 
>>
>> Please vote: do you approve the changes to the Code of Conduct proposed 
>> at https://github.com/sagemath/sage/pull/37501? Please vote on or before 
>> March 31.
>>
>> In case you want a summary: the old code of conduct was pretty short, so 
>> some details were added, and whole new sections were added. The proposed 
>> changes were greatly inspired by similar documents from the SciPy and 
>> NumFOCUS projects, and the proposed code now includes sections on 
>> diversity, how to report potential violations,  names of the committee 
>> members, and what is necessary to amend the document. There is also a new 
>> document, a manual for the Code of Conduct Committee, which describes what 
>> that committee does and what actions it might take to respond to reports. 
>> That document is a modified version of SciPy's corresponding document.
>>
>> -- 
>> John
>>
>>

-- 
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 
https://groups.google.com/d/msgid/sage-devel/4876cd47-f54f-4496-9601-509cf20b6d93n%40googlegroups.com.

Re: [sage-devel] Re: conda sage

2024-03-22 Thread C B

Sage in conda-forge is still 10.2

William Stein schrieb am Mittwoch, 13. März 2024 um 17:41:19 UTC+1:

> 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 questions regarding conda installation of 
>> sage.
>> It'd be great to have more visibility towards conda installation to 
>> attract more
>> users and developers in particular who can help out.
>>
>> Thanks,
>> Isuru
>>
>> On Sun, Mar 10, 2024 at 7:37 PM William Stein  wrote:
>>
>>> 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 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 people should install Miniforge, i.e., "(Discouraged as of 
 September 2023)".  We should update the instructions at 


 https://deploy-livedoc--sagemath.netlify.app/html/en/installation/conda#install-from-conda-forge

 since they recommend the now discouraged Mambaforge.

 The page https://github.com/conda-forge/miniforge suggests that 
 Mambaforge is somehow "just as good", but when I tried doing clean 
 installs, then installing Sage, I had the best experience (i.e., 
 completely 
 perfect!) with Miniforge, which is what they recommend.  Basically, we 
 should instead recommend:

 curl -L -O 
 https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-$(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 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 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 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"
>>>
>>
>> I'm using micromamba, which is supposed to be a drop in replacement 
>> for conda, but it just gives an error for the above, so maybe it is 
>> missing 
>> critical features needed to install sage:
>>
>> ---
>>
>> (compute-server-1540) ~/anaconda$ micromamba config --set 
>> channel_priority strict
>> The following arguments were not expected: strict channel_priority 
>> --set
>> Run with --help for more information.
>>
>> ---
>>
>> I'll revisit whether I need to switch to another conda...
>>
>> That said micromamba has strict by default:  
>> https://github.com/mamba-org/provision-with-micromamba/issues/33
>>
>> (compute-server-1540) ~/anaconda$ micromamba config --set 
>> channel_priority strict --help
>> Configuration of micromamba
>> Usage: /usr/local/bin/micromamba config [OPTIONS] [SUBCOMMAND]
>>
>> Options:
>>   -h,--help   Print this help message and exit
>>
>>
>> Configuration options:
>>   --rc-file TEXT ...  Paths to the configuration files to use
>>   --no-rc Disable the use of configuration files
>>   --no-envDisable the use of environment variables
>>
>>
>> Global options:
>>   -v,--verboseSet verbosity (higher verbosity with 
>> multiple -v, e.g. -vvv)
>>   --log-level ENUM:value in 
>> {critical->5,debug->1,error->4,info->2,off->6,trace->0,warning->3} OR 
>> {5,1,4,2,6,0,3}
>>   Set the log level
>>   -q,--quiet  Set quiet mode (print less output)
>>   -y,--yesAutomatically answer yes on prompted

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

On Fri, Mar 22, 2024 at 5:13 PM Matthias Koeppe 
wrote:

> Let me just point out that the idea that "grant has ended, so we can kill
> its deliverables" is fundamentally flawed, and certainly is not and cannot
> be the position of our project.
>
> Infrastructure grants are exactly set up for their longer-term and broader
> impacts.
>

the bundling with SageMath was rather artificial in this case, and anyway
OpenDreamKit had more deliverables which were not meant to be bundled at
all.

Nobody says "kill it".
It's a standalone  PyPI project which does not use anything in SageMath,
nor it is used from SageMath.
It can be installed from PyPI if anyone needs it.




>
> Matthias
>
> On Friday, March 22, 2024 at 5:58:47 AM UTC-7 Dima Pasechnik wrote:
>
>> I don't see any reason for pari-jupyter being a sage package. It has
>> nothing in common with sagelib, it's a standalone jupyter kernel for
>> Pari-GP.
>> It has ended up in sage in OpenDreamKit times, to make granting agency
>> happy.
>>
>>
>> On Thu, Mar 21, 2024 at 8:42 AM Edgar Costa  wrote:
>>
>>> Bill Allombert has been working on a kernel via xeus:
>>> https://pari.math.u-bordeaux.fr/git/xeus-gp.git/
>>> Which addresses many of the issues with the current one.
>>> While we for its first stable release, I recommend mine:
>>> https://github.com/edgarcosta/gp_kernel/
>>> where I have addressed many of the issues, by going through the route
>>> that every cell is a temporary file, which is loaded in gp.
>>>
>>>
>>> On Thu, Mar 21, 2024 at 4:29 AM Matthias Koeppe 
>>> wrote:
>>>
 - https://pypi.org/project/pari-jupyter/1.4.3rc1/
 - I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just
 point to the main sagemath repository
 - using WIP sage-project-cookiecutter to simplify maintenance
 https://github.com/sagemath/sage/pull/37541

 --
 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+...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/sage-devel/e822f186-6504-4516-9940-d03398f270b9n%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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x5FYigLmaKMc0wodYJB9BUqsdpyuy63RrxXoTcv%2BQKTJw%40mail.gmail.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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/c681d272-5561-4ef9-bdcc-33a1d503cee0n%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq2fci92VKp6c0mRxUt%2BVBzwBprMxQyENwsLa2n--uxHbw%40mail.gmail.com.

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

I wasn't advocating anything like that.  Certainly I don't think that 
pari-jupyter should be "killed".  I am assuming that pari-jupyter is or 
will be a package that can be installed with pip.  And I am also assuming 
that it has no direct interaction with Sage.  Are those assumptions wrong?  
If not, what benefit does the pari-jupyter project get from having it 
available as a sage spkg?

A question of more relevance to me is: do I need to add pari-jupyter to the 
Sage_macOS binary package, even though it could be installed separately by 
just running pip?  (We try to add all optional packages the we can build.). 
If installing pari-jupyter creates a kernel specification directory in 
/usr/local/share (as we do for the Sage kernel), then it will appear as an 
available kernel when jupyter is launched from the SageMath app, whether or 
not the location of the kernel is inside the app bundle.  How does it 
improve our user's experience to have the package installed inside of the 
app bundle, as opposed to in the user's Library/Python directory or inside 
the python.org framework?  While this question is specific to me, I think 
the same question applies to SageMath.

- Marc

On Friday, March 22, 2024 at 12:13:34 PM UTC-5 Matthias Koeppe wrote:

> Let me just point out that the idea that "grant has ended, so we can kill 
> its deliverables" is fundamentally flawed, and certainly is not and cannot 
> be the position of our project.
>
> Infrastructure grants are exactly set up for their longer-term and broader 
> impacts. 
>
> Matthias
>
> On Friday, March 22, 2024 at 5:58:47 AM UTC-7 Dima Pasechnik wrote:
>
>> I don't see any reason for pari-jupyter being a sage package. It has 
>> nothing in common with sagelib, it's a standalone jupyter kernel for 
>> Pari-GP.
>> It has ended up in sage in OpenDreamKit times, to make granting agency 
>> happy.
>>
>>
>> On Thu, Mar 21, 2024 at 8:42 AM Edgar Costa  wrote:
>>
>>> Bill Allombert has been working on a kernel via xeus:
>>> https://pari.math.u-bordeaux.fr/git/xeus-gp.git/
>>> Which addresses many of the issues with the current one.
>>> While we for its first stable release, I recommend mine: 
>>> https://github.com/edgarcosta/gp_kernel/
>>> where I have addressed many of the issues, by going through the route 
>>> that every cell is a temporary file, which is loaded in gp.
>>>
>>>
>>> On Thu, Mar 21, 2024 at 4:29 AM Matthias Koeppe  
>>> wrote:
>>>
 - https://pypi.org/project/pari-jupyter/1.4.3rc1/
 - I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just 
 point to the main sagemath repository
 - using WIP sage-project-cookiecutter to simplify maintenance 
 https://github.com/sagemath/sage/pull/37541

 -- 
 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+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/sage-devel/e822f186-6504-4516-9940-d03398f270b9n%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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x5FYigLmaKMc0wodYJB9BUqsdpyuy63RrxXoTcv%2BQKTJw%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/5337b5c3-49a7-4f35-9429-8d8351dc6115n%40googlegroups.com.

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

Let me just point out that the idea that "grant has ended, so we can kill 
its deliverables" is fundamentally flawed, and certainly is not and cannot 
be the position of our project.

Infrastructure grants are exactly set up for their longer-term and broader 
impacts. 

Matthias

On Friday, March 22, 2024 at 5:58:47 AM UTC-7 Dima Pasechnik wrote:

> I don't see any reason for pari-jupyter being a sage package. It has 
> nothing in common with sagelib, it's a standalone jupyter kernel for 
> Pari-GP.
> It has ended up in sage in OpenDreamKit times, to make granting agency 
> happy.
>
>
> On Thu, Mar 21, 2024 at 8:42 AM Edgar Costa  wrote:
>
>> Bill Allombert has been working on a kernel via xeus:
>> https://pari.math.u-bordeaux.fr/git/xeus-gp.git/
>> Which addresses many of the issues with the current one.
>> While we for its first stable release, I recommend mine: 
>> https://github.com/edgarcosta/gp_kernel/
>> where I have addressed many of the issues, by going through the route 
>> that every cell is a temporary file, which is loaded in gp.
>>
>>
>> On Thu, Mar 21, 2024 at 4:29 AM Matthias Koeppe  
>> wrote:
>>
>>> - https://pypi.org/project/pari-jupyter/1.4.3rc1/
>>> - I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just 
>>> point to the main sagemath repository
>>> - using WIP sage-project-cookiecutter to simplify maintenance 
>>> https://github.com/sagemath/sage/pull/37541
>>>
>>> -- 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/e822f186-6504-4516-9940-d03398f270b9n%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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x5FYigLmaKMc0wodYJB9BUqsdpyuy63RrxXoTcv%2BQKTJw%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/c681d272-5561-4ef9-bdcc-33a1d503cee0n%40googlegroups.com.

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

On Fri, Mar 22, 2024 at 3:01 PM Marc Culler  wrote:

> If one has Sage installed with the pari-jupyter package installed in Sage
> and one wants to run pari-jupyter, what does one do?  Is it equivalent to
> just installing pari-jupyter with pip and starting it up in the normal way?
>

I have pari+libpari installed systemwide. Then  installs pari-jupyter well
in a clean python 3.11 venv
Then I can run

pip install jupyterlab
jupyter kernelspec install --user
$(pwd)/share/jupyter/kernels/pari_jupyter


Then

jupyter lab

brings up a browser window with all the right notebooks, I can start
Pari-GP notebook, etc




> Does pari-jupyter use any components of Sage?  If the answers are "yes"
> and "no", then I agree that it is hard to see any reason why it should be a
> Sage package.
>

no, I don't think it does. Remove?

Dima


>
> - Marc
>
> On Friday, March 22, 2024 at 7:58:47 AM UTC-5 Dima Pasechnik wrote:
>
>> I don't see any reason for pari-jupyter being a sage package. It has
>> nothing in common with sagelib, it's a standalone jupyter kernel for
>> Pari-GP.
>> It has ended up in sage in OpenDreamKit times, to make granting agency
>> happy.
>>
>>
>> On Thu, Mar 21, 2024 at 8:42 AM Edgar Costa  wrote:
>>
>>> Bill Allombert has been working on a kernel via xeus:
>>> https://pari.math.u-bordeaux.fr/git/xeus-gp.git/
>>> Which addresses many of the issues with the current one.
>>> While we for its first stable release, I recommend mine:
>>> https://github.com/edgarcosta/gp_kernel/
>>> where I have addressed many of the issues, by going through the route
>>> that every cell is a temporary file, which is loaded in gp.
>>>
>>>
>>> On Thu, Mar 21, 2024 at 4:29 AM Matthias Koeppe 
>>> wrote:
>>>
 - https://pypi.org/project/pari-jupyter/1.4.3rc1/
 - I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just
 point to the main sagemath repository
 - using WIP sage-project-cookiecutter to simplify maintenance
 https://github.com/sagemath/sage/pull/37541

 --
 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+...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/sage-devel/e822f186-6504-4516-9940-d03398f270b9n%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+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x5FYigLmaKMc0wodYJB9BUqsdpyuy63RrxXoTcv%2BQKTJw%40mail.gmail.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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/2648a303-6b46-40d7-8a2e-1eb4f319e7ecn%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq3hnQBA%3DSRAnkC2ALCQD0fcbZGiCSrAKLYDwUu7wbUwCw%40mail.gmail.com.

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

If one has Sage installed with the pari-jupyter package installed in Sage 
and one wants to run pari-jupyter, what does one do?  Is it equivalent to 
just installing pari-jupyter with pip and starting it up in the normal 
way?  Does pari-jupyter use any components of Sage?  If the answers are 
"yes" and "no", then I agree that it is hard to see any reason why it 
should be a Sage package.

- Marc

On Friday, March 22, 2024 at 7:58:47 AM UTC-5 Dima Pasechnik wrote:

> I don't see any reason for pari-jupyter being a sage package. It has 
> nothing in common with sagelib, it's a standalone jupyter kernel for 
> Pari-GP.
> It has ended up in sage in OpenDreamKit times, to make granting agency 
> happy.
>
>
> On Thu, Mar 21, 2024 at 8:42 AM Edgar Costa  wrote:
>
>> Bill Allombert has been working on a kernel via xeus:
>> https://pari.math.u-bordeaux.fr/git/xeus-gp.git/
>> Which addresses many of the issues with the current one.
>> While we for its first stable release, I recommend mine: 
>> https://github.com/edgarcosta/gp_kernel/
>> where I have addressed many of the issues, by going through the route 
>> that every cell is a temporary file, which is loaded in gp.
>>
>>
>> On Thu, Mar 21, 2024 at 4:29 AM Matthias Koeppe  
>> wrote:
>>
>>> - https://pypi.org/project/pari-jupyter/1.4.3rc1/
>>> - I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just 
>>> point to the main sagemath repository
>>> - using WIP sage-project-cookiecutter to simplify maintenance 
>>> https://github.com/sagemath/sage/pull/37541
>>>
>>> -- 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-devel/e822f186-6504-4516-9940-d03398f270b9n%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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x5FYigLmaKMc0wodYJB9BUqsdpyuy63RrxXoTcv%2BQKTJw%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/2648a303-6b46-40d7-8a2e-1eb4f319e7ecn%40googlegroups.com.

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

+1

On Thursday, March 21, 2024 at 11:51:40 AM UTC-5 John H Palmieri wrote:

> Dear Sage community,
>
> As announced at 
> https://groups.google.com/g/sage-devel/c/Xf6dbPLmKPY/m/p88auKlBAwAJ, I 
> propose some changes to the Code of Conduct. Those changes have been 
> discussed and modified based on feedback from several developers: visit 
> https://github.com/sagemath/sage/pull/37501 for details. Those changes 
> are now ready for a vote here on sage-devel. 
>
> Please vote: do you approve the changes to the Code of Conduct proposed at 
> https://github.com/sagemath/sage/pull/37501? Please vote on or before 
> March 31.
>
> In case you want a summary: the old code of conduct was pretty short, so 
> some details were added, and whole new sections were added. The proposed 
> changes were greatly inspired by similar documents from the SciPy and 
> NumFOCUS projects, and the proposed code now includes sections on 
> diversity, how to report potential violations,  names of the committee 
> members, and what is necessary to amend the document. There is also a new 
> document, a manual for the Code of Conduct Committee, which describes what 
> that committee does and what actions it might take to respond to reports. 
> That document is a modified version of SciPy's corresponding document.
>
> -- 
> John
>
>

-- 
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 
https://groups.google.com/d/msgid/sage-devel/d7c29f58-9e0a-4c09-8c5c-4afd5c44ffc3n%40googlegroups.com.

Re: [sage-devel] pari-jupyter 1.4.3 release candidate

I don't see any reason for pari-jupyter being a sage package. It has
nothing in common with sagelib, it's a standalone jupyter kernel for
Pari-GP.
It has ended up in sage in OpenDreamKit times, to make granting agency
happy.


On Thu, Mar 21, 2024 at 8:42 AM Edgar Costa 
wrote:

> Bill Allombert has been working on a kernel via xeus:
> https://pari.math.u-bordeaux.fr/git/xeus-gp.git/
> Which addresses many of the issues with the current one.
> While we for its first stable release, I recommend mine:
> https://github.com/edgarcosta/gp_kernel/
> where I have addressed many of the issues, by going through the route that
> every cell is a temporary file, which is loaded in gp.
>
>
> On Thu, Mar 21, 2024 at 4:29 AM Matthias Koeppe 
> wrote:
>
>> - https://pypi.org/project/pari-jupyter/1.4.3rc1/
>> - I've added simple CODE_OF_CONDUCT and CONTRIBUTING files that just
>> point to the main sagemath repository
>> - using WIP sage-project-cookiecutter to simplify maintenance
>> https://github.com/sagemath/sage/pull/37541
>>
>> --
>> 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
>> https://groups.google.com/d/msgid/sage-devel/e822f186-6504-4516-9940-d03398f270b9n%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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x5FYigLmaKMc0wodYJB9BUqsdpyuy63RrxXoTcv%2BQKTJw%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/CAAWYfq0QBQVeqx61hiak3MOeAiBGFNrKv0xBi53yQKtdB-%3Dr5w%40mail.gmail.com.

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