#19851: Interpreter cell magics in Jupyter
-------------------------------------+-------------------------------------
       Reporter:  vbraun             |        Owner:
           Type:  defect             |       Status:  needs_review
       Priority:  major              |    Milestone:  sage-7.0
      Component:  interfaces         |   Resolution:
       Keywords:                     |    Merged in:
        Authors:  Volker Braun       |    Reviewers:
Report Upstream:  N/A                |  Work issues:
         Branch:                     |       Commit:
  u/vbraun/interpreter_cell_magics_in_jupyter|  
6f7176f3f9981af65af8fbb4724def5f9bae6d6e
   Dependencies:                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by charpent):

 Replying to [comment:13 vbraun]:

 Note : since my previous comment, I checked out develop, fetched and
 pulled 7.0rc0, made this new version, ptestlong'd it successfully,
 '''THEN''' created "mabranche" from 7.0rc0 and merged your branch into it.

 I still have the same problems, including no access to the reference
 manual from the "Help" menu of the notebook.

 > The R console error is old. This ticket changes nothing on that part
 anyways.

 I never met it. It is a '''serious''' bug, BTW. I never met it because I
 tend to mix Sage and R via a .Rnw file with R chunks interpreted in R (via
 knitr) and Sage chunks via Sagetex. The notebook is attracting because it
 allows this kind of mix much more easily (i.e. my students could use it,
 not only me...).

 > Your doc error is unrelated, too... this ticket changes nothing on the
 documentation.

 So why do I have error in your branch and not when I revert to develop
 (now at 7.0rc0) ?  '' "Every bug has (at least) a cause ! " '' (with
 apologies to Paracelse...). I agree, however, that your branch might well
 just '''reveal''' it...

 > I don't whats wrong, how did you install Sage in /usr anyways.

 That one is easy : I cloned the git repository in my home directory and
 {{{sido mv}}}'d it to /usr/local, '''THEN''' built it in place.

 > Are you sure you call the right sage install?

 I guess so :
 {{{
 charpent@asus16-ec:~$ which sage
 /usr/local/bin/sage
 charpent@asus16-ec:~$ ls -l `which sage`
 lrwxrwxrwx 1 root staff 12 oct.  27  2013 /usr/local/bin/sage ->
 ../sage/sage
 charpent@asus16-ec:~$ ls -l /usr/local/ | grep sage
 lrwxrwxrwx  1 root     staff       8 déc.  23 21:44 sage -> sage-7.0
 drwxr-sr-x 12 charpent charpent 4096 déc.  21 23:34 sage-6.10
 drwxr-sr-x 12 charpent charpent 4096 janv. 13 07:57 sage-7.0
 drwxr-sr-x 11 charpent charpent 4096 déc.  13 00:44 sage-exp
 drwxr-sr-x 12 charpent charpent 4096 déc.  12 11:11 sage-stable
 drwxr-sr-x 11 charpent charpent 4096 déc.  15 03:49 sage-test
 charpent@asus16-ec:~$ ls -l /usr/local/sage-7.0/sage
 -rwxr-xr-x 1 charpent charpent 4680 déc.  23 09:52
 /usr/local/sage-7.0/sage
 }}}


 > Where does /usr/local/sage/local/share/jupyter/kernels/sagemath/doc link
 to?
 Another easy one :
 {{{
 charpent@asus16-ec:~$ ls -l
 /usr/local/sage/local/share/jupyter/kernels/sagemath/doc
 lrwxrwxrwx 1 charpent charpent 42 janv. 13 20:41
 /usr/local/sage/local/share/jupyter/kernels/sagemath/doc ->
 /usr/local/sage-7.0/src/doc/output/html/en
 }}}
 which seems correct.

 Before you ask :
 {{{
 charpent@asus16-ec:~$ ls /usr/local/sage/src/doc/output/html/en/
 a_tour_of_sage     genindex.html  py-modindex.html  _static
 constructions      index.html     reference         thematic_tutorials
 developer          installation   search.html       tutorial
 faq                objects.inv    searchindex.js    website
 genindex-all.html  prep           _sources
 }}}

 HTH,

--
Ticket URL: <http://trac.sagemath.org/ticket/19851#comment:14>
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