On Friday, December 23, 2016 at 9:10:53 PM UTC+1, Jeroen Demeyer wrote: > > On 2016-12-23 10:34, Jean-Pierre Flori wrote: > > Maybe the code in sage/except.py should at least be modified not to > > modify the class of the exception. > > I guess you are talking about src/sage/interfaces/expect.py > Yes indeed.
> > Yes, that code is crazy when it comes to KeyboardInterrupt. Believe me, > it has been worse before and I already cleaned it up a little bit. > > If you have an explicit use case (as in: something that we could add a > doctest for), I could try to fix it. > Killing Magma? To be sure it quits quick you have to send two SIGINT's. It it just gets one it waits (for I don't know how long depending on what it's doing) before actually stopping its current computation. So my plan was to trigger a SIGALARM and send a couple of SIGINT's. And I used the alarm() stuff. But with it, except.py code gets the AlarmInterrupt and sends SIGINT to Magma and then waits for its prompt... I've not tested how bad it gets, that is: does it way forever? does Magma sometimes take ages to quit or not? So maybe that's overreacting but at first I got frustrated because Magma took longer than planned to quit even though it was not that longer... -- 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 sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
