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:56:26 +0800
commit0d76d2cb30fdaa0adbb151ecb4129789334b7beb (patch)
treee9d1ee50bab49232c85483d6477898dc51adf584 /doc
parent39c31cd95d9abdfa701431fca118526b7494fe74 (diff)
downloadoslo-i18n-0d76d2cb30fdaa0adbb151ecb4129789334b7beb.tar.gz
tox: Keeping going with docs3.25.0
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: If8c19a7d5d2a6ca089efb6c19d81a277aba7f06d
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 2d290be..2a8d917 100644
--- a/doc/requirements.txt
+++ b/doc/requirements.txt
@@ -2,7 +2,7 @@
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
-sphinx!=1.6.6,!=1.6.7,>=1.6.5,<2.0.0;python_version=='2.7' # BSD
-sphinx!=1.6.6,!=1.6.7,>=1.6.5;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.18.1 # Apache-2.0
reno>=2.5.0 # Apache-2.0