#13230: Should use a better sphinx patch to make documentation examples
interactive
---------------------------------+------------------------------------------
Reporter: pcpa | Owner: mvngu
Type: PLEASE CHANGE | Status: new
Priority: major | Milestone: sage-5.3
Component: documentation | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
---------------------------------+------------------------------------------
Comment (by pcpa):
To generate working documentation, I am currently using this hack:
{{{
%if %{with_sphinx_hack}
cp -far %{python_sitelib}/sphinx %{buildroot}%{python_sitearch}
sed -i "s|\(source.startswith('>>>')\)|\1 or source.startswith('sage:
')|" \
%{buildroot}%{python_sitearch}/sphinx/highlighting.py
%endif
[...]
%if %{with_sphinx_hack}
rm -fr %{buildroot}%{python_sitearch}/sphinx
%endif
}}}
I still think it would be better to find a better solution, like the
suggestion to use
{{{
.. code-block:: pycon
# sage: interactive code
}}}
but that probably would require patching almost every source file.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13230#comment:2>
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 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.
