summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorcaoyuan <cao.yuan@99cloud.net>2019-10-24 13:54:55 +0800
committercaoyuan <cao.yuan@99cloud.net>2019-10-24 13:58:31 +0800
commitec52c3b5dc94baed69de0de80f6c57bc244eaf25 (patch)
tree780456533877abe2c594b64111b2123c3914227a /doc
parente49eca232f272f011bdbfdf2770c45cb7c90bd20 (diff)
downloadoslo-concurrency-ec52c3b5dc94baed69de0de80f6c57bc244eaf25.tar.gz
tox: Keeping going with docs
Sphinx 1.8 introduced [1] the '--keep-going' argument which, as its name suggests, keeps the build running when it encounters non-fatal errors. This is exceptionally useful in avoiding a continuous edit-build loop when undertaking large doc reworks where multiple errors may be introduced. [1] https://github.com/sphinx-doc/sphinx/commit/e3483e9b045 Change-Id: Id12730272782a7cfda89cba79d40919e2a5ecd24
Diffstat (limited to 'doc')
-rw-r--r--doc/requirements.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/requirements.txt b/doc/requirements.txt
index 25408d9..00b94af 100644
--- a/doc/requirements.txt
+++ b/doc/requirements.txt
@@ -2,8 +2,8 @@
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
# this is required for the docs build jobs
-sphinx!=1.6.6,!=1.6.7,>=1.6.2,<2.0.0;python_version=='2.7' # BSD
-sphinx!=1.6.6,!=1.6.7,!=2.1.0,>=1.6.2;python_version>='3.4' # BSD
+sphinx>=1.8.0,<2.0.0;python_version=='2.7' # BSD
+sphinx>=1.8.0,!=2.1.0;python_version>='3.4' # BSD
openstackdocstheme>=1.20.0 # Apache-2.0
reno>=2.5.0 # Apache-2.0
fixtures>=3.0.0 # Apache-2.0/BSD