#10191: Catch fatal Sphinx errors
---------------------------------------------------+------------------------
Reporter: jdemeyer | Owner:
GeorgSWeber
Type: defect | Status: closed
Priority: major | Milestone: sage-4.6.1
Component: build | Resolution: duplicate
Keywords: sphinx build docbuilder documentation | Author:
Upstream: N/A | Reviewer: Jeroen
Demeyer
Merged: | Work_issues:
---------------------------------------------------+------------------------
Changes (by jdemeyer):
* status: needs_review => closed
* author: Jeroen Demeyer =>
* reviewer: => Jeroen Demeyer
* resolution: => duplicate
* merged: sage-4.6.1.alpha0 =>
Old description:
> Ensure that the building of Sage aborts after a fatal Sphinx error. The
> build still continues after non-fatal errors or warnings.
>
> The attached patch does this by raising a Python exception if Sphinx
> fails.
> Apply [attachment:10191_catch_sphinx_error.patch]
>
> Follow-up ticket: #10200
New description:
Ensure that the building of Sage aborts after a fatal Sphinx error. The
build still continues after non-fatal errors or warnings.
The attached patch does this by raising a Python exception if Sphinx
fails.
Obsoleted by #10200
--
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10191#comment:16>
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.
