On 19/04/15 12:49, Marc Mezzarobba wrote: > On my machine, sage -t
--verbose src/sage/rings/integer.pyx blocks on:
>
> Trying (line 6089): alarm(0.5); (2^100).binomial(2^22,
algorithm='pari')
> Expecting:
> Traceback (most recent call last):
> ...
> AlarmInterrupt
>
> Is that a known problem?
For the report I got the very same problem on sage-6.7.beta2 (while
doing some long tests).
If I do the following in a console, it looks fine
sage: from time import time
sage: a = ZZ(2)^100
sage: b = ZZ(2)^22
sage: while True:
....: t0 = time()
....: alarm(0.5)
....: try:
....: a.binomial(b, algorithm='pari')
....: except AlarmInterrupt:
....: print "alarm after {}".format(time() - t0)
alarm after 0.500133991241
alarm after 0.50009393692
alarm after 0.500094175339
alarm after 0.500092983246
...
If I write the very same code in a file and run
sage: %runfile test_file.py
then nothing happens! If I do a Ctrl-C (KeyboardInterrupt) then I got a
strange AlarmInterrupt after:
Traceback (most recent call last):
...
KeyboardInterrupt:
sage:
AlarmInterrupt
sage:
Is it related?
Vincent
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
