#19132: Start a single process when running Sage
-------------------------------------+-------------------------------------
Reporter: jdemeyer | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.9
Component: interfaces | Resolution:
Keywords: | Merged in:
Authors: Jeroen Demeyer | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/jdemeyer/fix_interrupts_in_jupyter|
a281e344e30955987df1d696b25b18f452c5a218
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Description changed by jdemeyer:
Old description:
> Jupyter assumes that it is running a single process. With Sage, this
> assumption is currently not true due to the "front-end" `$SAGE_ROOT/sage`
> script. If we instead use `exec` there and apply #19135, this is no
> longer a problem.
New description:
Jupyter assumes that it is running a single process, otherwise interrupts
get sent to the wrong process. With Sage, this assumption is currently not
true due to the "front-end" `$SAGE_ROOT/sage` script. If we instead use
`exec` there and apply #19135, this is no longer a problem and Sage
Jupyter notebooks can be interrupted properly.
--
--
Ticket URL: <http://trac.sagemath.org/ticket/19132#comment:8>
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.
