I do recall a system python upgrade on Fedora a while ago where python was replaced/updated in a way that was binary incompatible. As a result, my source-built sage was rendered non-functional. Recompiling worked but of course "make" wouldn't find which prerequisites were changed and hence which components required rebuild. So there is a consistency-managing issue with basing manually-built software on components that are automatically updated. We already have that problem, though. It may be a reason to push conda-managed environments a little more: same problem, but now only localized to conda.
These events are rare, because most python updates are binary-compatible. Version bumps in python would be another source, but at least on fedora that is mitigated by having separate packages for each python version. Hence, one would normally have several python versions on the system after a while and the flavour of python for which your sage would normally still be around. On Tuesday, 1 April 2025 at 08:57:06 UTC-7 David Lowry-Duda wrote: > On 10:50 Tue 01 Apr 2025, Trevor Karn wrote: > >This is my concern. But if there is a way to use only system python > >installed following https://www.python.org/about/gettingstarted/ without > >regard to version issues, and get rid of SPKG python, then that makes > sense > >to me. > > I think sage currently checks for python >= 3.11. I don't know what > features that uses, but this is newer than what comes with several major > distributions. For example, Ubuntu 20.04 LTS uses python 3.8 as its system > python, and Ubuntu 22.04 LTS uses python 3.10 as its system python. > > - DLD > -- 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/a02a103b-e64a-4a7f-aa68-46a51b1c0355n%40googlegroups.com.
