On Saturday, February 17, 2024 at 11:13:33 AM UTC-8 Dima Pasechnik wrote:
On 17 February 2024 17:16:07 GMT, Matthias Koeppe <matthia...@gmail.com> wrote: >I share the same concern based on the amplification of the failure >probability, due to the large number of dependencies in Sage. My proposal is in fact aimed at reducing the number of pinned Sage dependecies, drastically. As you seem to be responding to what I wrote there, I have to point out that it is the *unpinning*, not the *pinning*, that is the concern for instability that Nathan and I share. Because most of them are either dependencies of Jupyterlab, or of Sphinx, or of Python build system, and none of the them should be Sage's concern to package, with all their dependencies. If you itch to pack the said dependencies, please do it in a separate repo/PyPI package, which can be consumed by sagelib to get the desired pinned dependencies (and test all this in the existing CI, why not?) But stop tying them up with sagelib - which in effect forces people interested in sagelib to slave away on packaging 300 dependencies, most of which aren't even tested by CI in any way, besides building. Please liberate sagelib from the cabal of the ftontend, etc. Sagemath is not a disto - no sane distro puts everything in one flat directory structure. Sagemath is an insane pile of needlessly vendored packages. Wow, there's so much to unpack here... -- 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/cf23d2b4-be5a-45f4-ac6d-f1922ce140f3n%40googlegroups.com.
