On Sat, May 11, 2013 at 6:19 PM, Nils Bruin <nbr...@sfu.ca> wrote: > On May 11, 2:15 pm, Thierry <sage-googlesu...@lma.metelu.net> wrote: >> Hi, >> >> it was reported >> inhttp://ask.sagemath.org/question/2567/kill-the-thread-in-a-long-compu... >> that cython seems not to handle Python signals correctly. It-it a >> feature or should-it be reported ? > > I think it's a feature. There's a lot of code that reacts badly to > being interrupted by signals. If I'm not mistaken, most of our code > runs with signals disabled. It's the responsibility of the library > function authors to insert sig_on and sig_off things to allow > occasional signals to be processed when doing so is safe. Apparently > that didn't happen for `factor`!
No, it did happen with factor (in fact, that might be one of the first functions that motivated me to write the first sig_on/sig_off). If you look at the ask.sagemath discussion, you'll see everything got sorted out, and mainly there was a mistake in the original poster's code. They had written something silly and got confused about the order of evaluation. William -- 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 http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
