On Friday 19 April 2024 at 20:08:51 UTC+2 Matthias Koeppe wrote:
On Friday, April 19, 2024 at 5:08:02 AM UTC-7 Martin R wrote: 2.) If this is about dependencies on other software, why aren't the distributions named after these dependencies? Martin, I have answered this already when you asked it in the PR: Some are. Matthias, this does not answer my question. Maybe it is clearer if I ask: why do you introduce distributions sage-graphs, sage-combinat, sage-categories etc. Martin Note that the description of the PR where you asked this question contains the list of the distributions: https://github.com/sagemath/sage/pull/36676 "We restructure the all.py files for modularization. Guided by the technical constraints outlined in https://groups.google.com/g/sage-devel/c/ozh-7ZZ848s, https://github.com/sagemath/sage/pull/35095 defines distribution packages (pip-installable packages) sagemath-{brial, combinat, eclib, flint, gap, giac, glpk, graphs, groups, homfly, lcalc, libbraiding, libecm, linbox, modules, mpmath, ntl, pari, plot, polyhedra, schemes, singular, standard-no-symbolics, symbolics}." My June 2023 sage-devel post https://groups.google.com/g/sage-devel/c/kiB32zP3xD4 explained that the design use "... 3 types of distribution packages: - Packages that are named after a basic mathematical structure but may cover a wide range of generalizations/applications of this structure. - Packages that are named after an upstream library. - Packages that are named after a technical functionality." -- 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/092e1914-061a-4c41-90df-669921679959n%40googlegroups.com.
