Dear sage-devel,

It seems to me that the interrupt-handling function sig_check() is not not so well known. I created the documentation ticket #16902 to remedy this, it would be good if somebody who is not too familiar with signals could review this and tell me whether it's clear enough.

The short version is: if you are just running your own Cython code without calls to external libraries, then sig_check() instead of sig_on() is probably the better choice. Moreover, sig_check() is a lot safer and easier to use.

Jeroen.


PS: another interrupt-related ticket which needs review is #16233.

--
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.
For more options, visit https://groups.google.com/d/optout.

Reply via email to