On 2025-03-30 14:19:21, Dima Pasechnik wrote:
> I propose to remove python3 (and sqlite - which has no other consumers)
> from the list of Sage spkgs (packages).
> Anno 2025 one has sufficiently many non-Sage ways to make sure a good
> enough python3 is available for use with Sage.
This is no longer a huge issue for me because we now have a way to
install only the sage library, but I still agree in principle and it
would be nice to start cleaning out the source tree. Our python
requirements are not crazy, and we already require some version of
python to be installed. Python is available on all operating systems
from multiple sources. Building it from scratch is the worst of those
because it makes us tech support for the OS toolchain. Every "python
failed to build" report is really a "python from the OS was not
detected" report in disguise, which we first have to explain.
The other argument in favor of keeping it has been that it allows for
easy testing, by bumping the SPKG version and letting the CI run. This
is still true I guess, but
1. No one is currently doing it
2. There are several people continuously testing sage with new
dependencies using other methods
3. Shipping complexity to users to make the lives of developers
easier is the opposite of how we should do things
--
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 visit
https://groups.google.com/d/msgid/sage-devel/Z-sy8YjThruYJN7H%40mertle.
