invoke sphinx directly instead of through pbr

The pbr feature for invoking sphinx doesn't let us treat warnings as
errors because of a bug in pbr. Switch to invoking sphinx directly,
including removing the setup.cfg instructions for sphinx, so we can use
the flag to treat warnings as errors. Doing this also requires fixing a
few existing warnings, so those changes are included in this patch.

Change-Id: I2aa0d844855d5a18646d0bc3907620544ae71be2
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2016-04-14 11:24:31 -04:00
parent 0553b9a5a3
commit 97986ff795
5 changed files with 12 additions and 1 deletions

View File

@ -66,6 +66,7 @@ series. You can find the detail of the various release series here:
bexar/index
austin/index
releases/*
schedules/*
Series-Independent Releases
===========================

View File

@ -17,3 +17,8 @@ Documentation:
.. deliverable::
:series: mitaka
.. toctree::
:hidden:
schedule

View File

@ -8,3 +8,8 @@ Release schedule: :doc:`schedule`
.. deliverable::
:series: newton
.. toctree::
:hidden:
schedule

View File

View File

@ -53,7 +53,7 @@ commands = {toxinidir}/tools/build_tag_history.sh {toxinidir}
#commands = python setup.py testr --coverage --testr-args='{posargs}'
[testenv:docs]
commands = python setup.py build_sphinx
commands = sphinx-build -a -E -W -d doc/build/doctrees -b html doc/source doc/build/html
deps = .[sphinxext]
[flake8]