On Thursday, 5 February 2026 at 17:09:05 UTC-8 [email protected] wrote:

Also, I just got bit by the hidden magic cython recompiling everything (and 
I don't know what I did to cause it either). Thankfully my computer is 
powerful and fast, it only took 10 minutes to do whatever it needed to do 
(which I don't know because I didn't enable the meson verbose on this 
computer).

Python files are okay since they are basically instantaneous, but Cython 
files are a different beast. IMO the proper thing to do would be to revert 
this feature (to what is effectively the status quo) and **first** have a 
proper discussion about whether we want it or not.


As far as I can see, a recompile (or at least a significantly longer 
start-up time) for sage is triggered whenever some packages have been 
upgraded (so a "dnf update" on a fedora system, for instance). I don't know 
which package updates trigger this. Is it a new python becoming available? 
It should really just stick to the python it's configured with and only 
change upon reconfiguration.

In a lot of cases it will not be necessary to do the recompile: even if a 
library got updated, it's probably still capable of resolving the same 
symbols as the previous version sage was compiled against.

It is a problem if people run "automatic" updates on their machines (which 
is somewhat doable nowadays): then it becomes totally unpredictable whether 
sage will recompile or not. Really, in that case part of the post-install 
cleanup should be "run/recompile sage". It looks like dnf can be configured 
to have "post-transaction-actions" but that's a big ask from users.

Perhaps we do need to recommend conda installs in stronger terms, to 
insulate the sage install more from system updates.



-- 
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 [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/sage-devel/b6f1cbd0-ac7f-47af-94c0-0ddf267d2fd5n%40googlegroups.com.

Reply via email to