On Sunday, August 11, 2024 at 8:05:42 AM UTC-7 Marc Culler wrote: The real driver of the complexity, then, is the number of different versions of python which Sage is obliged to support
Sure. My current implementation of the "sage --package create --pypi" for these types of packages does not even bother to filter out any of the unsupported Python versions - so you see a bunch of "cp38" files (https://github.com/sagemath/sage/blob/fdc545367173f836890b9cddbce0d7c032b10d2b/build/pkgs/rpds_py/checksums.ini#L196) ... and also win32 and win_amd64 files ( https://github.com/sagemath/sage/blob/fdc545367173f836890b9cddbce0d7c032b10d2b/build/pkgs/rpds_py/checksums.ini#L316). Easy to refine, but I think it's good enough for now. When I build Sage for the macOS app my current process [...] Sage ends up with current (as of the time of my build) versions of jupyterlab and notebook, and those two packages end up having the dependencies against which they have actually been tested. I do the same in upgrade PRs such as https://github.com/sagemath/sage/pull/38471 (needs review). Just updating every Jupyter-related package to the latest and then running with "pip check" whether any of the declared version bounds for dependencies are violated. (Thanks to your code to extract runtime dependencies from PyPI wheels that is now part of "sage --package create --pypi", preparing such upgrades has become much smoother.) (I don't believe that even a project as large as jupyter has the capacity to test against all combinations of dependencies which would meet their specifications, but I do believe that they test pretty thoroughly against the newest allowed version of each dependency.) I agree. I do a sanity check to see that the installed versions of jupyterlab and notebook work at a basic level, using the Sage kernel [...] I think it would be be valuable to prepare a checklist for making such updates and add it to our developer documentation. I think Eric Gourgoulhon has some Jupyter notebooks that are a good test of graphics and typesetting, some of which is Sage-specific. -- 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/18d05328-4443-4251-a13d-0bdc30bf8620n%40googlegroups.com.
