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
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
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 enviro
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 ou
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 e
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 d
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
"Mai
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
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
+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
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 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
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
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 2
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+l
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
+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 o
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 ha
+1
On Thursday, March 21, 2024 at 4:51:40 PM UTC 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 f
FWIW, this is working again on 10.3
On Tue, 27 Feb 2024 at 22:41, Jan Groenewald
wrote:
> Hi
>
> sage 10.2 on Debian 12, and
> sage -i jupyterlab
>
> sage --notebook=jupyterlab
>
> launches, and the logo displays and animates, and then stops. I can't get
> further. Any ideas?
>
> This was workin
20 matches
Mail list logo
