summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDouglas Mendizábal <dmendiza@redhat.com>2019-10-01 09:18:28 -0500
committerAndreas Jaeger <aj@suse.com>2019-10-02 15:16:56 +0200
commitcafa14b00fd098ff98a5da592e5b9634cabb4c00 (patch)
treec9921117d9bdc8bbbd54d041274447c29a27b6eb
parentb9f3375ddd792f06a67fcf0eb7b98ddf463a6b87 (diff)
downloadpython-barbicanclient-cafa14b00fd098ff98a5da592e5b9634cabb4c00.tar.gz
Fix lower-constraints tox target
We seem to be running into a coverage issue [1] in 4.0. This patch raises the lower bound of coverage to 4.1 to get the lower-constraints target to pass again. Update sphinx requirements to match global-requirements. [1] https://github.com/nedbat/coveragepy/issues/359 Change-Id: Ieddef753b4ee3e9b6d246168ed17c5c99e084564 (cherry picked from commit 79f387fbd5fde9e671dd32684f73dbf3451379dc)
-rw-r--r--doc/requirements.txt3
-rw-r--r--lower-constraints.txt2
-rw-r--r--test-requirements.txt2
3 files changed, 4 insertions, 3 deletions
diff --git a/doc/requirements.txt b/doc/requirements.txt
index 827758f..23ba973 100644
--- a/doc/requirements.txt
+++ b/doc/requirements.txt
@@ -1,5 +1,6 @@
# The order of packages is significant, because pip processes them in the order
# 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.2 # BSD
+sphinx>=1.6.2,!=1.6.6,!=1.6.7,<2.0.0;python_version=='2.7' # BSD
+sphinx>=1.6.2,!=1.6.6,!=1.6.7;python_version>='3.4' # BSD
openstackdocstheme>=1.18.1 # Apache-2.0
diff --git a/lower-constraints.txt b/lower-constraints.txt
index 9a616b8..587efd3 100644
--- a/lower-constraints.txt
+++ b/lower-constraints.txt
@@ -4,7 +4,7 @@ Babel==2.3.4
cffi==1.7.0
cliff==2.8.0
cmd2==0.8.0
-coverage==4.0
+coverage==4.1
cryptography==2.1
debtcollector==1.2.0
decorator==3.4.0
diff --git a/test-requirements.txt b/test-requirements.txt
index da9fdc7..55a823b 100644
--- a/test-requirements.txt
+++ b/test-requirements.txt
@@ -1,7 +1,7 @@
# The order of packages is significant, because pip processes them in the order
# of appearance. Changing the order has an impact on the overall integration
# process, which may cause wedges in the gate later.
-coverage!=4.4,>=4.0 # Apache-2.0
+coverage!=4.4,>=4.1 # Apache-2.0
hacking>=1.1.0,<1.2.0 # Apache-2.0
fixtures>=3.0.0 # Apache-2.0/BSD
requests-mock>=1.2.0 # Apache-2.0