summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorcaoyuan <cao.yuan@99cloud.net>2019-10-24 14:09:59 +0800
committercaoyuan <cao.yuan@99cloud.net>2019-10-24 14:21:22 +0800
commit1e7a0c6fbb9782b7fc0216430e3a84e9249014f4 (patch)
tree2de3ce6b56f528f48cf52f079ee829c10ebb1a31 /doc
parentc01b03e87c66e964100d3d56d91b0f5f045e6190 (diff)
downloadoslo-messaging-1e7a0c6fbb9782b7fc0216430e3a84e9249014f4.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: If9885a1f064226909181d8b69241eb814deb2105
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 cb837c3..a6e137e 100644
--- a/doc/requirements.txt
+++ b/doc/requirements.txt
@@ -3,8 +3,8 @@
# process, which may cause wedges in the gate later.
openstackdocstheme>=1.20.0 # Apache-2.0
-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
reno>=2.5.0 # Apache-2.0
# imported when the source code is parsed for generating documentation: