On Friday, 17 October 2025 at 16:14:41 UTC-7 [email protected] wrote: On Fri, Oct 17, 2025 at 4:01 PM Travis Scrimshaw <[email protected]> wrote:
I have verified that this does work, but it does so silently. It is also very dangerous because it can easily look that Sage is taking a long time to load because, say, you touched element.pxd trivially. I don't see what's "dangerous" here. If you touched element.pxd then, by right, anything dependent on it must be rebuilt one way or another. Anyhow, you can (as documented, see src/doc/en/installation/source.rst - or the corresponding place in the html docs) do export MESONPY_EDITABLE_VERBOSE=1 Then when you start ./sage, you will see if any building is taking place. This is certainly surprising compared to how sage used to work: it would start up normally, pick up changes from .py files and run with whatever the latest compile of pyx files was. I definitely agree that the new way sounds more consistent in most cases, but https://xkcd.com/1172/ comes to mind. You have to let the community know when you make changes like that! Even if it's a change for the better on the whole, people will be *unpleasantly* surprised when it happens without them asking for it. People could be running code where timestamps on pyx files get updated arbitrarily, so they'd prefer the old behaviour (because they knew it wasn't indicative of inconsistent state). I would definitely prefer to have the verbose on by default so that at least I get an indication that the system is doing *something*. -- 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/e538deee-4c07-4395-8588-39630e2ba467n%40googlegroups.com.
