On 9 April 2025 18:54:13 GMT-05:00, Nils Bruin <nbr...@sfu.ca> wrote:
>On Wednesday, 9 April 2025 at 16:44:31 UTC-7 dim...@gmail.com wrote:
>
>As I already explained, it's quite a stretch by Sage's standards to call 
>python3 package standard. Because it is not tested enough; 
>because few months into release, the supposedly stable Sage release is 
>often not installable, not the least due to rapidly aging Python 
>toolchain. 
>
>Are you saying that python source distributions bitrot particularly 
>quickly? Is there something particular about python that breaks their 
>source distributions so quickly? If that's the case, I think that's 
>concerning in itself. 

it's not unusual for some "move fast and break things" OS vendors to change 
APIs in incompatible ways, update toolchains in incompatible ways, e.g. Apple 
does it quite often, as we learned over the years. And do not forget rolling 
release OSes.

python (minor) releases come up every 2 months, sometimes every month. I gather 
it's in response to the OS updates, in part.

Our releases are less frequent, and we often don't  check that Sage works on 
such and such  betas and pre-releases.


> It should be possible to build a python source 
>distribution that is a few years old without a problem, right? 

no, not really. On some Linux OSes like Debian, some open-source BSDs perhaps, 
on others much less so.

E.g. Apple's XCode update released a short while ago has broken Sage 10.6. (as 
the C++ compiler got a version bump).

Vendors of maths soft should not want to come close to components which closely 
interact with the OS, such as compilers and interpreters, unless they just 
cannot avoid it. In case of Python it's surely beneficial not to come close to 
it, as Python's vendor does a very good job in doing ptompt updates, a surely a 
much better job than our attempts to vendor them.
Same applies to compilers.


> Its 
>prerequisites shouldn't be breaking their APIs on such short timescales. 

Tell this to Apple,  RedHat (i.e. IBM). :-)

Dima

> 
>

-- 
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/E173794E-FFA5-48FA-9634-C98B8BEB70C5%40gmail.com.

Reply via email to