On Sun, Apr 13, 2025 at 12:32 AM 'tobia...@gmx.de' via sage-devel < sage-devel@googlegroups.com> wrote:
> Marc, what is your opinion about replacing "building from source" in the > Python spkg by "installing the prebuild pythons from > astral/python-build-standalone"? > Hi Tobias, I don't know anything about astral. But I am not at all concerned about being able to build python or find a pre-built python. That is easy. My concern is how to populate the Sage venv with such a python in a way which is guaranteed to work with the full Sage build process. Since the Sage build process is about to change in some unspecified way about which I cannot predict any details, this conscern cannot be addressed until those changes are in place. Once the changes are in place, our build process will have to be changed to match, as will the process of making the Sage build self-contained and relocatable and the process of assembling the app. I would like to make those changes to our process one time only, rather than have to redo them for each iteration of this transition of Sage's build process. All I am asking is to leave the current python3 spkg "build from source" option in place, protected by requiring a special configure option to trigger its use, until these coming changes to Sage are in place and have become stabilized. Please explain to me why that is such an unreasonable request. We have heard repeatedly that everything we need to do is totally trivial, while this seemingly totally trivial request proposed by Nils is an unbelievably difficult thing which no one has any idea how to achieve. It is pretty hard to buy that. - 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/CALcZXRFQw8iypuitWE%3Db1CS_uOao0TL63Bf9agudJCsEuWg-GQ%40mail.gmail.com.
