As we are doing the IPython update now, I thought of this thing again and I
totally forgot how complex this is.
One way to solve this, is to cancel any alarm after evaluating input. That
should solve the problem, but I have no idea if this is acceptable or not.
I didn't find a way to see, if an
On Thu, Feb 7, 2019 at 5:05 PM E. Madison Bray wrote:
>
> On Thu, Feb 7, 2019 at 4:53 PM Jeroen Demeyer wrote:
> >
> > On 2019-02-07 16:45, E. Madison Bray wrote:
> > > Apparently Jeroen argued about this with the IPython developers some
> > > time ago: https://github.com/ipython/ipython/pull/986
On Thu, Feb 7, 2019 at 4:53 PM Jeroen Demeyer wrote:
>
> On 2019-02-07 16:45, E. Madison Bray wrote:
> > Apparently Jeroen argued about this with the IPython developers some
> > time ago: https://github.com/ipython/ipython/pull/9867
>
> Indeed. Your post did seem familiar to me, but I actually for
On 2019-02-06 20:52, Nils Bruin wrote:
This is the same as in python:
>>> import signal
>>> signal.alarm(1)
0
>>> Alarm clock
It looks like this is just the default signal handler for python (the
one that just prints the signal name and exits)
For the record, that message "Alarm clock" is
On 2019-02-07 16:45, E. Madison Bray wrote:
Apparently Jeroen argued about this with the IPython developers some
time ago: https://github.com/ipython/ipython/pull/9867
Indeed. Your post did seem familiar to me, but I actually forgot about
that discussion.
--
You received this message because
On Thu, Feb 7, 2019 at 4:14 PM E. Madison Bray wrote:
>
> On Thu, Feb 7, 2019 at 4:13 PM E. Madison Bray wrote:
> >
> > On Wed, Feb 6, 2019 at 8:52 PM Nils Bruin wrote:
> > >
> > > On Wednesday, February 6, 2019 at 6:35:27 AM UTC-8, E. Madison Bray wrote:
> > >>
> > >>
> > >> Which is being reac
On Thu, Feb 7, 2019 at 4:13 PM E. Madison Bray wrote:
>
> On Wed, Feb 6, 2019 at 8:52 PM Nils Bruin wrote:
> >
> > On Wednesday, February 6, 2019 at 6:35:27 AM UTC-8, E. Madison Bray wrote:
> >>
> >>
> >> Which is being reached because AlarmInterrupt is a subclass of
> >> KeyboardInterrupt . I
On Wed, Feb 6, 2019 at 8:52 PM Nils Bruin wrote:
>
> On Wednesday, February 6, 2019 at 6:35:27 AM UTC-8, E. Madison Bray wrote:
>>
>>
>> Which is being reached because AlarmInterrupt is a subclass of
>> KeyboardInterrupt . I don't know why this doesn't happen then when,
>> say, mashing Ctrl-C.
On Wednesday, February 6, 2019 at 6:35:27 AM UTC-8, E. Madison Bray wrote:
>
>
> Which is being reached because AlarmInterrupt is a subclass of
> KeyboardInterrupt . I don't know why this doesn't happen then when,
> say, mashing Ctrl-C. I guess because IPython installs its own SIGINT
> handle
On Wed, Feb 6, 2019 at 10:29 AM jonathan.kliem via sage-devel
wrote:
>
> sage: alarm(1)
> sage:
>
> AlarmInterrupt escaped interact()
>
> sage:
> sage:
> ^[[50;1R
> **
>
> Oops, Sage crashed. We do our best to make it stable, but.
sage: alarm(1)
sage:
AlarmInterrupt escaped interact()
sage:
sage:
11 matches
Mail list logo
