On Saturday, April 19, 2025 at 7:12:16 AM UTC+8 Nils Bruin wrote: So a middle ground would be to offer a security blanket during the transition: change the default behaviour of the python package for now to NOT build, but as a transition measure offer a configuration flag that restores the ability to build python from source. The clear goal of that must be that within the near future, no-one is actually activating that configuration flag, after which it can be removed with minimal impact. Once the python package has become just a stub to test if there is a python available that works properly, it will be easy to remove the package and instead make the test for python a normal prerequisite check.
Alternatively, the python-spkg could be changed to install python via `uv python install 3.13` (instead of building from source). Then the public contract doesn't change and there is no impact for end-users (i.e. the configure + make workflow keeps unchanged even if one doesn't have a suitable python installed already), it's just the underlying implementation that changes. It's similar to how some of the python packages are now installed via their binary wheel instead of building them from source. -- 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/a49d5a24-e5bc-4b0b-a949-0568938c528an%40googlegroups.com.
