Sorry, what "feature" you want to revert? We're not going back to setuptools.
Besides, I doubt it was recompiling everything in sagelib, for this you really need something extraordinary like "make clean", or upgrading Cython, or I don't know. But yes, if you don't have "--disable-doc" on, then indeed meson is slow in processing the docs. Someone needs to get their hands dirty with it and remove 15 years of technical debt we accumulated on building docs. Dima On Thu, Feb 5, 2026 at 7:09 PM Travis Scrimshaw <[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. > > Travis > > On Thursday, February 5, 2026 at 11:39:43 AM UTC+9 Travis Scrimshaw wrote: >> >> Okay, thanks. That helped a lot and made it so I could fix my compile-time >> issues. >> >> That said, there is absolutely *no* way anybody except a sage build system >> expert could have found and known to do that. Also, I had no idea I should >> even look at meson/ninja logs for cython errors (much less where they would >> be located) either. >> >> We need proper displaying of error messages when builds fail. The generic >> slop I posted is completely unhelpful (thankfully, I knew it was a Cython >> compile issue because of what I was changing, but imagine if I didn't; e.g., >> a bad branch merge). There is a balance to be had, but we need more general >> verbosity in starting Sage when its running (potentially time consuming) >> build steps. >> >> Unfortunately I don't even have enough time to do the code I really need to >> do (even more so for should), nor do I have the expertise to help with the >> build system stuff. >> >> >> On Thursday, February 5, 2026 at 1:20:54 AM UTC+9 [email protected] wrote: >> >> On February 4, 2026 8:57:21 AM CST, "'[email protected]' via sage-devel" >> <[email protected]> wrote: >> >> On Wednesday, February 4, 2026 at 3:09:10 PM UTC+1 [email protected] wrote: >> >> 2b) Revert "sage -b" to actually just rebuilding the parts of Sage that >> should be rebuilt/recompiled; meson is not part of this AFAIK. >> >> after https://github.com/sagemath/sage/pull/41174 >> "sage -b" does >> >> ninja -C $SAGE_ROOT/build/sage-distro >> >> (you can also run this explictly) >> >> Tobias says it's not 100% fool-proof from meson point of view, but it's >> certainly fast and should very quickly rebuild >> what's needed. >> >> >> That's good to hear at least. >> >> Best, >> Travis > > -- > 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/ebf355f3-7713-4e01-a773-0cfd6c63eedan%40googlegroups.com. -- 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/CAAWYfq2guGDNNSM1UNf7GxQPGS5WKP36UNGyty%2B_15q4APeEfg%40mail.gmail.com.
