On Saturday, December 24, 2016 at 10:22:13 AM UTC+1, Jeroen Demeyer wrote: > > On 2016-12-23 21:49, Jean-Pierre Flori wrote: > > > > > > 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? > > If Magma needs a "special" trick to get interrupted, you should just > modify the interrupt() method in sage/interfaces/magma.py > You need this special trick to kill it. My issue is that I can not use the alarm() machinery to trigger it...
-- 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.
