[sage-devel] Re: Package upgrade PRs waiting for review

I've set the first one to needs work since it changes some versions in the pyproject.toml (which specifies the depenendies of sagelib). Since the PR doesn't include any other changes in sagelib, I don't think these stricter version constraints for sagelib make sense and should be reverted. On

[sage-devel] Re: Proposal: Demote jupyter-jsmol and tachyon to optional

On Tuesday, August 20, 2024 at 5:42:42 PM UTC-7 John H Palmieri wrote: I just built Sage on an OS X machine with a bunch of homebrew packages installed. It took under 20 minutes to build everything except the documentation, while the file sagemath_doc_html-none.time says real 24m20.264s [...] w

Re: [sage-devel] Re: Proposal: Demote jupyter-jsmol and tachyon to optional

On 21/08/24 13:22, Kwankyu Lee wrote: On Wednesday, August 21, 2024 at 9:42:42 AM UTC+9 John H Palmieri wrote: ... maybe we should consider distributing all of the documentation pre-built as a tarball, not just some png files. (I have resisted this in the past, but I am changing my

[sage-devel] Re: Proposal: Demote jupyter-jsmol and tachyon to optional

On Wednesday, August 21, 2024 at 9:42:42 AM UTC+9 John H Palmieri wrote: ... maybe we should consider distributing all of the documentation pre-built as a tarball, not just some png files. (I have resisted this in the past, but I am changing my mind.) Packages that are necessary to build the do

[sage-devel] Re: Proposal: Demote jupyter-jsmol and tachyon to optional

On Tuesday, August 20, 2024 at 6:45:41 AM UTC-7 Kwankyu Lee wrote: On Tuesday, August 20, 2024 at 7:07:54 PM UTC+9 Eric Gourgoulhon wrote: There are tons of png files in the "3d Graphics" section of the documentation: https://doc.sagemath.org/html/en/reference/plot3d/sage/plot/plot3d/plot3d.

[sage-devel] Re: Proposal: Demote jupyter-jsmol and tachyon to optional

On Wednesday, August 21, 2024 at 2:57:31 AM UTC+9 Matthias Koeppe wrote: I'll note that playwright can also used by Jupyter to export notebooks in PDF format. (For details, see ticket description of https://github.com/sagemath/sage/pull/38509) That elevates playwright to be a somewhat natural

[sage-devel] Package upgrade PRs waiting for review

build/pkgs/numpy 2.0.1, scipy 1.13.1, cmake 3.30.2, gsl 2.8, meson 1.5.1, meson_python 0.16.0, ninja_build 1.12.1, openblas 0.3.28, pybind11 2.13.1, pythran 0.16.1 build/pkgs/tachyon: Fix rpath build/pkg

[sage-devel] Re: Proposal: Policy for standard packages from binary wheels

On Tuesday, August 20, 2024 at 10:54:22 AM UTC-7 Nils Bruin wrote: What is currently not clear to me is *where* those binary wheels are going to come from The upstream project is building them and depositing them on PyPI. and how we're going to test/ensure that they are available for the pl

Re: [sage-devel] Proposal: Demote jupyter-jsmol and tachyon to optional

On Tuesday 20 August 2024 at 06:54:00 UTC-7 Michael Orlitzky wrote: [...] As a distro package, tachyon is mildly annoying, but all that it really needs is a sane build system. The existing one is a case study in what happens when you try to recreate autotools in undocumented Makefile fragments.

[sage-devel] Re: Proposal: Demote jupyter-jsmol and tachyon to optional

On Monday, August 19, 2024 at 11:46:32 PM UTC-7 Kwankyu Lee wrote: If taking screenshots from 3d graphics automatically for pdf documentation is the only reason to consider playwright [...] I'll note that playwright can also used by Jupyter to export notebooks in PDF format. (For details, see

Re: [sage-devel] Proposal: Demote jupyter-jsmol and tachyon to optional

On Tuesday, August 20, 2024 at 7:04:36 AM UTC-7 Ricardo Buring wrote: As an alternative to (automatically) opening a web browser, Just to clarify, the web browser is not "opened" in the sense of popping up on the screen. It's done by playwright in a headless operation. perhaps one could auto

Re: [sage-devel] Proposal: Demote jupyter-jsmol and tachyon to optional

On Tuesday, August 20, 2024 at 6:54:00 AM UTC-7 Michael Orlitzky wrote: As a distro package, tachyon is mildly annoying, but all that it really needs is a sane build system. The existing one is a case study in what happens when you try to recreate autotools in undocumented Makefile fragments. U

[sage-devel] Re: Proposal: Policy for standard packages from binary wheels

On Tuesday 20 August 2024 at 10:03:59 UTC-7 Matthias Koeppe wrote: On Tuesday, August 20, 2024 at 9:02:14 AM UTC-7 julian...@fsfe.org wrote: I consider this approved. While I don't think I would be opposed to the proposal here, I believe that our policy says that for a disputed PR to be "appr

[sage-devel] Re: Proposal: Policy for standard packages from binary wheels

You also mentioned the PR in your quote. I just wanted to clarify that the PR itself is not approved. I am glad that we agree on this :) julian On Tuesday, August 20, 2024 at 8:03:59 PM UTC+3 Matthias Koeppe wrote: > On Tuesday, August 20, 2024 at 9:02:14 AM UTC-7 julian...@fsfe.org wrote: > >

[sage-devel] Re: message marked as off topic

On Tuesday, August 20, 2024 at 8:56:15 AM UTC-7 julian...@fsfe.org wrote: implies that "disputed" label is only for a PR that has positive review from a reviewer but another still objects it. I think adding "disputed" label prematurely is not appropriate. Then who can remove the "disputed" labe

[sage-devel] Re: Proposal: Policy for standard packages from binary wheels

On Tuesday, August 20, 2024 at 9:02:14 AM UTC-7 julian...@fsfe.org wrote: I consider this approved. While I don't think I would be opposed to the proposal here, I believe that our policy says that for a disputed PR to be "approved," a vote needs to happen here or on the PR. Julian, you snip

[sage-devel] Re: Proposal: Policy for standard packages from binary wheels

I consider this approved. While I don't think I would be opposed to the proposal here, I believe that our policy says that for a disputed PR to be "approved," a vote needs to happen here or on the PR. The implementation of the binary wheel infrastructure in https://github.com/sagemath/sa

[sage-devel] Re: message marked as off topic

implies that "disputed" label is only for a PR that has positive review from a reviewer but another still objects it. I think adding "disputed" label prematurely is not appropriate. Then who can remove the "disputed" label in this case? That's not how I interpret the policy we have. I think

Re: [sage-devel] Proposal: Demote jupyter-jsmol and tachyon to optional

As an alternative to (automatically) opening a web browser, perhaps one could automate (three.js) exporting to glTF and a small renderer (raylib?) generating the image. Best, Ricardo -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscrib

Re: [sage-devel] Proposal: Demote jupyter-jsmol and tachyon to optional

Playwright (via Chromium) would add another non-portable component to sage, which incidentally downloads several hundred megabytes of untrusted executable code from god-knows-where. As a distro package, tachyon is mildly annoying, but all that it really needs is a sane build system. The existing o

[sage-devel] Re: Proposal: Demote jupyter-jsmol and tachyon to optional

On Tuesday, August 20, 2024 at 7:07:54 PM UTC+9 Eric Gourgoulhon wrote: There are tons of png files in the "3d Graphics" section of the documentation: https://doc.sagemath.org/html/en/reference/plot3d/sage/plot/plot3d/plot3d.html It would be quite a burden to maintain this manually. Meanwhil

[sage-devel] Re: Proposal: Demote jupyter-jsmol and tachyon to optional

Le mardi 20 août 2024 à 08:46:32 UTC+2, Kwankyu Lee a écrit : As far as I remember from the discussion in https://github.com/sagemath/sage/issues/33513, saving 3d graphics to png files is already possible from the menu "Save as PNG". Indeed, this works well from the threejs menu, but this h