On Friday, 11 April 2025 at 15:55:39 UTC-7 marc@gmail.com wrote:
The obvious questions which this raises and which have still not been
answered here are: What is so wrong with this process? Why do we have to
break it? Why can't we at least leave the Sage spkg in place until there
is an
On Sat, Apr 12, 2025 at 1:01 PM Nils Bruin wrote:
I get the impression that the concern is about maintenance load: when the
> project takes on the commitment to build python then it must update the
> python build package whenever this is required for supporting current
> operating systems. Appare
On 12 April 2025 14:33:03 GMT-05:00, Marc Culler wrote:
>On Sat, Apr 12, 2025 at 1:01 PM Nils Bruin wrote:
>
>I get the impression that the concern is about maintenance load: when the
>> project takes on the commitment to build python then it must update the
>> python build package whenever th
Marc, what is your opinion about replacing "building from source" in the
Python spkg by "installing the prebuild pythons from
astral/python-build-standalone"? Would this work for the MacOS app; and if
not why?
Other popular projects, like anki and influxdb, seem to use these builds
for their e
On Saturday, April 12, 2025 at 9:57:50 PM UTC-5 Dima wrote:
this is what many users need - to be able to install Sage into an existing
Python environment; thus support is provided for a range of pythons.
That is what I said in my last message. There is no need to repeat it back
to me.
Cat
On Sat, Apr 12, 2025 at 8:48 PM Marc Culler wrote:
>
> On Saturday, April 12, 2025 at 9:57:50 PM UTC-5 Dima wrote:
>
> this is what many users need - to be able to install Sage into an existing
> Python environment; thus support is provided for a range of pythons.
>
>
> That is what I said in my
