#16902: Advertise sig_check() better in the developers manual
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: enhancement | Status: needs_work
Priority: minor | Milestone: sage-6.4
Component: documentation | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers: Vincent Delecroix
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/ticket/16902 | 26a3edcd203369c1fb1e9d9561c998f9abe671cd
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:9 dimpase]:
> it should better be `Python statement`.
I could change this.
> Or any Python statement?
> And what is the role of the word `possible` there? I don't get it.
I mean that Python code can sometimes raise a `KeyboardInterrupt`, but I
also don't know exactly when this happens. For example, the following can
be interrupted:
{{{
cython('while True: print "foo"')
}}}
But the following cannot be interrupted:
{{{
cython('while True: x = ["foo"] * 100')
}}}
--
Ticket URL: <http://trac.sagemath.org/ticket/16902#comment:11>
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.
