#18512: Move notebook() into Sage
------------------------+----------------------------
Reporter: vbraun | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.8
Component: notebook | Keywords:
Merged in: | Authors:
Reviewers: | Report Upstream: N/A
Work issues: | Branch:
Commit: | Dependencies:
Stopgaps: |
------------------------+----------------------------
Right now the `notebook()` function is a lazy import from sagenb. Hence
any access (like looking at the docstring) imports sagenb which changes
the display backend which causes various problems (see
https://groups.google.com/d/msg/sage-devel/3uaY6xHLMqQ/Zyn67xJ0LaMJ). It
also doesn't fit into a world where there is more than one notebook. And
its current behavior of turning the current Sage session into a notebook
server can't work with the IPython notebook or SMC.
First, we should definitely move `notebook` into the Sage library to move
it away from sagenb.
The more general question is what to do with it then. Options are
* Just let it launch SageNB, any other notebook needs to be launched via
`sage --notebook=...` on the commandline
* Deprecate `notebook()` altogether
* Let `notebook()` always spawn an independent process, and add an
argument to select which one
--
Ticket URL: <http://trac.sagemath.org/ticket/18512>
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.
