I am taking care of this in #40888. Reviews welcome I also opened an issue to deal with porting to Python 3.14, #40890
Dima On September 25, 2025 5:35:22 PM CDT, Nils Bruin <[email protected]> wrote: >On Thursday, 25 September 2025 at 06:38:45 UTC-7 [email protected] wrote: > >This is because rather than using the supplied python3.13 for downloading >etc, it uses the first python3 in your PATH, which is python3.14. And in >the latter FancyURLopener has been removed. > >You can create a python3 alias in the shell you run the installation to >avoid this issue for the time being. > >alias python3=python3.13 > > >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) > > >-- >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/3d689a1a-6ee6-49be-a0a0-d7994460d722n%40googlegroups.com. -- 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/C30BEED5-2249-4ED1-B954-C196395D80FA%40gmail.com.
