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 <edgardi...@gmail.com> >>>> 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 <matthia...@gmail.com> >>>>> 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 >>>>>> >>>>>> <https://groups.google.com/d/msgid/sage-devel/e822f186-6504-4516-9940-d03398f270b9n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- >>>>> 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 >>>>> >>>>> <https://groups.google.com/d/msgid/sage-devel/CA%2BiQ7x5FYigLmaKMc0wodYJB9BUqsdpyuy63RrxXoTcv%2BQKTJw%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- 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/18a665cb-535a-43ce-ba87-26ae57ffe346n%40googlegroups.com.
