#19877: Add SageNB exporter, Jupyter extension
-------------------------------------+-------------------------------------
       Reporter:  vbraun             |        Owner:
           Type:  enhancement        |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-7.0
      Component:  packages:          |   Resolution:
  standard                           |
       Keywords:                     |    Merged in:
        Authors:  Volker Braun       |    Reviewers:  Nicolas ThiƩry, Eric
                                     |  Gourgoulhon, Benjamin Ragan-Kelley,
                                     |  Karl-Dieter Crisman
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/vbraun/add_sagenb_exporter__jupyter_extension|  
a89993a9228ed4960dc1f972b3b195f438bf998a
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by kcrisman):

 > Jupyter notebooks are a single file and not an opaque directory full of
 stuff. This is a fundamental design choice and not going to change. About
 the only thing we can do is prevent people from writing new SageNB
 notebooks so their data doesn't end up in an evolutionary dead end.

 So in a Jupyter notebook one would include other data in a more 'Pythonic'
 way?  We'd want fairly good documentation on how to do that (as well as
 the below).

 >
 > Jupyter interacts have a slightly different syntax
 > {{{
 > from ipywidgets import interact, IntSlider
 > @interact
 > def _(n=IntSlider(3)):
 >     print n^2
 > }}}
 > One might write a compatibility layer so that the old SageNB interact
 syntax still works, thats not something that belongs on this ticket.
 I see.  That's too bad that it's not in the global namespace for Sage
 Jupyter worksheets, perhaps could be addressed there.  Making interacts
 more difficult to do is a regression (completely irrespective of the whole
 default or exporting question).  As a different question, would Jupyter
 notebooks be able to support the "extended" syntax that SMC and Sage cell
 support (e.g. nested interacts)?

 > Accordingly, I would suggest to set the ticket to positive review. Do
 you agree?

 I think I'm okay with that as long as it's not (yet) the default notebook
 for continuing users.  We need a solution of some kind for the above two
 issues before that.  Please cc: me on any such tickets - once created I
 think we can set this to positive review, yes.

--
Ticket URL: <https://trac.sagemath.org/ticket/19877#comment:54>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to