#16902: Advertise sig_check() better in the developers manual
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: needs_info
Priority: minor | Milestone: sage-6.4
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/ticket/16902 | 313d884ab090c89dbaaa2a6958166d053e99627a
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:3 vdelecroix]:
> 1) `sig_on/sig_off` is Sage specific or is it included within Cython? It
would be worth mentioning it. If it is Sage specific, why is that? and how
do people coding in Cython do? (seems to be `with nogil`). If it is
shipped with Cython, there should a pointer toward its documentation.
It is completely Sage-specific, I guess other people writing Cython code
do not care about interrupts. There has been talking about putting these
in Cython, but that has not happened yet.
> 2) If it is none, it is still interesting to mention it within a stack
of calls like
> {{{
> def f1():
> sig_on()
> x = f2()
> sig_off()
> # ...
>
> def f2():
> sig_on()
> # ...
> sig_off()
> return ans
> }}}
Good suggestion!
> 3) The section `Releasing the Global Interpreter Lock (GIL)` was a bit
obscure to me. It would be nice to have one sentence to say what it is. I
guess it is related to my remark 1.
It is one of those things where, if you don't know it, you don't need to
care. But I can put a link to the Cython documentation.
> 4) After reading the implementation of `alarm` I wonder why using
`alarm` in doctests rather than directly the `setitimer` from the `signal`
library?
Because `alarm()` is much cleaner.
> It is basically in `TESTS` blocks that such test
> would appear, and involving there the `signal` library is not ugly
Why is it not ugly?
> and people reading it will learn about it instead of learning Sage
wrapper!
If people care about Sage's wrapper, they can still figure out the
implementation and can find out about `setitimer` that way.
--
Ticket URL: <http://trac.sagemath.org/ticket/16902#comment:4>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" 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-trac.
For more options, visit https://groups.google.com/d/optout.
