On Thursday, 25 September 2025 at 16:11:07 UTC-7 [email protected] wrote: I am taking care of this in #40888. Reviews welcome
I also opened an issue to deal with porting to Python 3.14, #40890 Both those tickets have the laudable goal of getting sage to work with Python 3.13. That absolutely has to happen, so it's great you're working on that. My request was about another issue: so ... ./configure --with-system-python3=python3.13 does NOT work to build sage with a different python. Would it be possible to fix sage configure to actually be able to configure which python to build with? As this example shows, it's a desirable feature to have. Does that need a ticket? (the alias solution needs to be executed every time and looks like something that should be injected into sage-env or something like that) Even though we'd love that sage always supports the latest python as soon as possible, the reality is that one can find oneself in the situation where "python3" on a computer is NOT a python with which sage can work. In that situation, it would be good if there's a workaround: point sage at another python. The proposed "configure" does that probably to some extent, but as observed, there's an additional "alias" required. That needs to stick somehow. Can we make configure do the job? Or is "conda" in that situation the better option (conda goes through great lengths to customize environments where all kinds of system utilities are specifically configured, regardless of the defaults provided by the host. Getting Python 3.14 supported will put that problem under the radar for a while. Probably until Python 3.15 comes along. But it will pop up again. -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/sage-support/ae0177d2-11cf-43e8-af59-61e2b72fd1d0n%40googlegroups.com.
