In fact I don't understand alarm(...) at all. Maybe it works better on
linux or older OS X releases, but on the OS X machines to which I have
access, it feels broken. If I do:
sage: alarm(0.3)
then after 0.3 seconds I see a message
KeyboardInterrupt escaped interact()
That's fine. But then
Perhaps related, and I also see this with 10.3.beta1: after using
alarm(...), Sage does not exit gracefully.
% ./sage
┌┐
│ SageMath version 10.3.beta2, Release Date: 2023-12-13 │
│ Using Python 3.11.6. Type
Thanks for the report. editables was missing a dependency; this is fixed
in https://github.com/sagemath/sage/pull/36885
On Friday, December 15, 2023 at 4:32:56 AM UTC-8 furutaka@gmail.com
wrote:
> I tried to build this version on two Fedora-39 machines.
> The build completed w/o any
On Thursday, December 14, 2023 at 4:05:31 PM UTC John H Palmieri wrote:
On OS X (both Intel and Apple Silicon) I'm getting a lot of new failures,
many of the form "Killed due to alarm":
sage -t --long --random-seed=144845266083009760424007645487960076680
I tried to build this version on two Fedora-39 machines.
The build completed w/o any problem on one machine, but failed on another
(at work) when building editables;
after doing `./sage -pip install flit_core` in the build environment, the
build seemed to be continuing (I had to leave work before
