On Monday, January 27, 2014 10:00:38 PM UTC-8, Georgi Guninski wrote:
>
> On Mon, Jan 27, 2014 at 11:17:50AM -0800, John H Palmieri wrote:
> >
> > First, please try to be more polite.
> >
>
> Dear sir or madam,
>
> Observe that in sage 5.12 there is no cancel_alarm().
>
Yes, there is, defi
On Mon, Jan 27, 2014 at 11:17:50AM -0800, John H Palmieri wrote:
>
> First, please try to be more polite.
>
Dear sir or madam,
Observe that in sage 5.12 there is no cancel_alarm().
> Second, the old alarm code happened to work the way you wanted, but it
> wasn't documented that way, and it's
On 2014-01-27 18:35, Georgi Guninski wrote:
On linux:
$man alarm
If seconds is zero, no new alarm() is scheduled.
In any event any previously set alarm() is canceled.
Linux/Unix alarm() is not Sage alarm()...
If you want the direct system call, use the Python interface
signal.alarm() instead
On Monday, January 27, 2014 9:35:55 AM UTC-8, Georgi Guninski wrote:
>
> On Mon, Jan 27, 2014 at 06:19:34PM +0100, Jeroen Demeyer wrote:
> > On 2014-01-27 15:13, Georgi Guninski wrote:
> > >On Mon, Jan 27, 2014 at 03:07:00PM +0100, Jeroen Demeyer wrote:
> > >>On 2014-01-27 14:35, Jeroen Demeye
On Mon, Jan 27, 2014 at 06:19:34PM +0100, Jeroen Demeyer wrote:
> On 2014-01-27 15:13, Georgi Guninski wrote:
> >On Mon, Jan 27, 2014 at 03:07:00PM +0100, Jeroen Demeyer wrote:
> >>On 2014-01-27 14:35, Jeroen Demeyer wrote:
> >>>Use cancel_alarm(). I agree this should be documented in alarm().
> >>
On 2014-01-27 15:13, Georgi Guninski wrote:
On Mon, Jan 27, 2014 at 03:07:00PM +0100, Jeroen Demeyer wrote:
On 2014-01-27 14:35, Jeroen Demeyer wrote:
Use cancel_alarm(). I agree this should be documented in alarm().
This is now http://trac.sagemath.org/ticket/15743 and needs review.
May I
On Mon, Jan 27, 2014 at 03:07:00PM +0100, Jeroen Demeyer wrote:
> On 2014-01-27 14:35, Jeroen Demeyer wrote:
> >Use cancel_alarm(). I agree this should be documented in alarm().
>
> This is now http://trac.sagemath.org/ticket/15743 and needs review.
>
May I ask you to allow alarm(0) again since o
On 2014-01-27 14:35, Jeroen Demeyer wrote:
Use cancel_alarm(). I agree this should be documented in alarm().
This is now http://trac.sagemath.org/ticket/15743 and needs review.
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe fr
On Mon, Jan 27, 2014 at 02:35:55PM +0100, Jeroen Demeyer wrote:
> On 2014-01-27 10:57, Georgi Guninski wrote:
> >How to cancel a pending alarm()?
> Use cancel_alarm(). I agree this should be documented in alarm().
>
Thanks.
--
You received this message because you are subscribed to the Google Gr
On 2014-01-27 10:57, Georgi Guninski wrote:
How to cancel a pending alarm()?
Use cancel_alarm(). I agree this should be documented in alarm().
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving em
I am running code in a loop and certain function might take
long or short time. I don't want to wait long and
want to continue with the fast cases.
Up to sage 5.12 I used:
alarm(5)
try:
F=mightbelong(n)
alarm(0) #to not fire later
except Key
11 matches
Mail list logo