#9426: Docbuilder ignores return code from subprocess.call()
-----------------------------+----------------------------------------------
Reporter: leif | Owner: mvngu
Type: defect | Status: new
Priority: major | Milestone:
Component: documentation | Keywords: Sphinx documentation builder error
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-----------------------------+----------------------------------------------
Comment(by leif):
Replying to [comment:6 jhpalmieri]:
> Should a docbuild error just cause an exception to be raised, thus
ending the build? That wouldn't be hard to implement, I think.
I would have implemented that if I felt it was appropriate. ;-)
An error in a single document should IMHO not stop / break the whole
build, but should be propagated and reported (also) at the end, in a
summary. Same for warnings, but even harder to implement. (See also
#10200.)
I actually do not understand why we do an equivalent of `os.system("sphinx
...")`; as far as I know, Sphinx is itself written in Python and its
functionality should therefore be directly accessible to us from the
`builder.py` script. This way we would easily get the warnings as well.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9426#comment:7>
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.
