I completely understand that change is hard, and that the new workflow came as a surprise. I should have communicated this earlier and in more detail — that’s on me.
To clarify, the behavior under the new build system is *standard for meson‑python editable installs*: when the library is installed in editable mode, changes in Python or Cython files are picked up simply by restarting, without needing a full rebuild (https://mesonbuild.com/meson-python/how-to-guides/editable-installs.html). The same approach is used by NumPy, SciPy, and others. In my experience, it generally works quite nice and rebuilds for the usual changes to one or two Cython modules are often picked-up without any noticable delay. Personally, I don't mind that it's silently recompiling in the background, but can understand that personal preferences differ there. We can certainly set the toggle to 'loud', but that would need more testing (eg some doctests might fail because they directly check the output of sage). I suggest to give it a bit of time and see how it feels in practice. Once people have actually used it for a while, we’ll have a clearer sense of what’s genuinely problematic versus what just takes getting used to, and we can revisit adjustments then. On Sunday, October 19, 2025 at 6:18:41 AM UTC+8 [email protected] wrote: > On Sunday, October 19, 2025 at 1:41:41 AM UTC+9 Michael Orlitzky wrote: > > On 2025-10-18 08:43:13, Travis Scrimshaw wrote: > > Okay, perhaps I should be more precise here (it's also been awhile since > I > > used one, so my memory might be wrong). On any single command, it > doesn't > > say anything (it would be difficult for it to say what it was doing), > but > > when run from a makefile, I thought it did output what command was being > > run? (Okay, technically that isn't a C compiler either...but the act of > > compiling a C program.) > > "make" will print the commands it's running, but I was not seriously > trying to nitpick, your point was clear. When you run GCC, you expect > it to be compiling a C program; when you run Sage, you expect to see a > Sage banner. > > My earlier message was not defending the behavior, only pointing out > that spin doesn't solve it. If you are willing to forego the editable > install, then meson alone works great. If not, the problem lies one > level below spin. > > > I know, but I think it is important to make sure the point can't be > defeated by technicalities. :) > -- 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/5e1a559a-ac9f-4c66-b540-2e010a8e718an%40googlegroups.com.
