#6586: [with spkg, needs review] update Sphinx to version 0.6.2 or 0.6.3
--------------------------+-------------------------------------------------
Reporter: jhpalmieri | Owner: mabshoff
Type: enhancement | Status: new
Priority: major | Milestone: sage-4.1.2
Component: packages | Keywords:
Reviewer: Mitesh Patel | Author: John Palmieri
Merged: |
--------------------------+-------------------------------------------------
Old description:
> As the summary says. The spkg can be found at
>
> http://sage.math.washington.edu/home/palmieri/SPKG/sphinx-0.6.2.p0.spkg
New description:
As the summary says. The spkg can be found at
http://sage.math.washington.edu/home/palmieri/SPKG/sphinx-0.6.3.p1.spkg
After installing it and before building any docs, you will probably need
to delete the directory SAGE_ROOT/devel/sage/doc/output -- this holds
cached information which may not be compatible between different versions
of Sphinx.
Sphinx 0.6.3 also uses Jinja2. Sage includes Jinja, not Jinja2. As long
as you're connected to a network, the installation of Sphinx 0.6.3
downloads Jinja2 and installs it -- it can coexist with Jinja, so it
shouldn't mess anything up. If you're not connected to a network, and for
putting in the Sage tar ball, there is an spkg for Jinja2:
http://sage.math.washington.edu/home/palmieri/SPKG/jinja2-2.1.1.p0.spkg
Finally, the patch below ("inheritance_example.patch") is not required.
It provides an illustration of a new capability of Sphinx 0.6.3 (and I
think it's quite nice), but it's not something that needs to be installed
or reviewed for this ticket.
--
Comment(by jhpalmieri):
To cremona: sorry about that. When you switch versions of Sphinx, you
have to delete the old output in the docs directory -- it caches some
information there, apparently in ways which are not compatible between
versions. So after you install the spkg, delete the directory
SAGE_ROOT/devel/sage/doc/output and try again. I should change the
summary on this ticket to reflect this...
To timdumol: I see, jinja and jinja2 can coexist on the same system, so
for now we can have both. That's the best solution now, I agree. (I
tried replacing all of the "import jinja" lines with "import jinja2", but
there was a problem with one of them: in sage.ext.gen_interpreters, the
line {{{from jinja.datastructure import ComplainingUndefined}}} doesn't
translate, because there is no jinja2.datastructure.)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/6586#comment:49>
Sage <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en
-~----------~----~----~----~------~----~------~--~---
