On Sunday, December 25, 2016 at 8:22:33 PM UTC+1, Jeroen Demeyer wrote:
>
> On 2016-12-25 12:55, Jean-Pierre Flori wrote:
> >
> >
> > On Sunday, December 25, 2016 at 10:32:11 AM UTC+1, Jeroen Demeyer wrote:
> >
> > On 2016-12-24 13:30, Jean-Pierre Flori wrote:
> > > I just want to
On 2016-12-25 12:55, Jean-Pierre Flori wrote:
On Sunday, December 25, 2016 at 10:32:11 AM UTC+1, Jeroen Demeyer wrote:
On 2016-12-24 13:30, Jean-Pierre Flori wrote:
> I just want to kill Magma
M.quit() should work.
Sure, but how do I trigger a call to M.quit() iin the middle of
On Sunday, December 25, 2016 at 10:32:11 AM UTC+1, Jeroen Demeyer wrote:
>
> On 2016-12-24 13:30, Jean-Pierre Flori wrote:
> > I just want to kill Magma
>
> M.quit() should work.
>
Sure, but how do I trigger a call to M.quit() iin the middle of a long
computation?
--
You received this mess
On 2016-12-24 13:30, Jean-Pierre Flori wrote:
I just want to kill Magma
M.quit() should work.
--
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+unsubsc
On Saturday, December 24, 2016 at 11:00:33 AM UTC+1, Jeroen Demeyer wrote:
>
> On 2016-12-24 10:37, Jean-Pierre Flori wrote:
> > My issue is that I can not use the alarm() machinery to trigger it...
>
> I do not understand why you would want to use alarm() to kill magma. It
> seems like an ins
On 2016-12-24 10:37, Jean-Pierre Flori wrote:
My issue is that I can not use the alarm() machinery to trigger it...
I do not understand why you would want to use alarm() to kill magma. It
seems like an instance of the XY problem (http://xyproblem.info/) to me,
where X=killing magma and Y=usin
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 cod
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 gu
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.
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, that code is crazy when it comes to KeyboardInterrupt. Believe me,
it has been
On Friday, December 23, 2016 at 7:58:11 AM UTC+1, Jeroen Demeyer wrote:
>
> On 2016-12-22 11:25, Jean-Pierre Flori wrote:
> > Dear all,
> >
> > First question: Is there are fundamental differences btw using the
> > cysignal alarm function and the one from the signal module?
>
> Depends what
On 2016-12-22 11:25, Jean-Pierre Flori wrote:
Dear all,
First question: Is there are fundamental differences btw using the
cysignal alarm function and the one from the signal module?
Depends what you mean with "fundamental". The internal implementation is
different. The main user-visible diff
Dear all,
First question: Is there are fundamental differences btw using the cysignal
alarm function and the one from the signal module?
Second question: Is there any reason to make AlarmInterrupt derive from
KeyboardInterrupt?
SIGALARM and SIGINT are different signals.
And its troublesome when
13 matches
Mail list logo
