On Mon, Apr 7, 2025 at 3:25 PM Dima Pasechnik wrote: > > It's not standard - no-one nowadays builds Sage's Python, not even CI is > doing this. > > This is the point I already made. > You are the sole users of this semi-broken feature. >
Well, it is a feature that is available by just setting one configure option, and we have used the feature with Sage 9.3, 9.4, 9.5, 9.6, 9.7, 9.8, 10.0, 10.1, 10.2, 10.3, 10.4, 10.5 and 10.6 without encountering a single failure of the python3 spkg. Moreover you have not been able to produce an example of a build that failed because of the python3 spkg. Your macOS example had actually failed on a different spkg that gets built before the python3 spkg, and the cause was a misconfigured homebrew installation. Your Ubuntu 24.04 on WSL example failed in the same way when the system python 3.12 was installed and available. So while I do observe that a lot of your time is being spent debugging Sage build failures for users, and I certainly appreciate that effort, there seems to be no evidence at all that removing the python3 spkg will reduce the amount of that time. Moreover, Nils' proposal would prevent anyone from accidentally using the python3 spkg, so that should ensure that none of the build failures reported to the Sage project would be failures of the python3 spkg. - Marc -- 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/CALcZXRGQ7p3QPQpkzo3a-ZAeZaMiuU3mH0_igFGxmUY6E39Jsw%40mail.gmail.com.
