On Monday, 7 April 2025 at 08:59:40 UTC-7 marc....@gmail.com wrote: If the Python spkg were removed we would no longer be able to start from a standard build of Sage.
Can you explain what the non-standard part would be and why you are concerned it would be more fragile on the side of Sage? To me it looks you would start out with building python much in the same way as how it now gets built by sage's python3 package and then in the ensuing environment you would end up building sage in a completely standard way, with the python requirement satisfied by the python build you have just completed. Given that the python build would complete *before* you even get started on building sage, I would expect that this doesn't affect the fragility of the sage build at all. Are you worried that sage would have trouble recognizing the python build as valid for its purposes? If anything, I'd expect that if sage would not be providing its own python package, it would be forced to be more tolerant on what python to accept. So I can see how giving away full control of python could make *sage* more fragile, but at the same time we are already relying on externally provided pythons in many cases and that doesn't seem to cause huge problems. -- 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/7c6e0caf-6007-433d-baad-bcdb93ee40d2n%40googlegroups.com.
