summaryrefslogtreecommitdiff
path: root/test-requirements.txt
diff options
context:
space:
mode:
authorzhoulinhui <df.some@foxmail.com>2020-09-18 00:24:11 +0800
committerzhoulinhui <df.some@foxmail.com>2020-10-16 01:19:42 +0000
commit82a792f201ca45b1043d46c744a24cd36b1580f5 (patch)
tree9972244f7519c20e5a12676e790bafcbf542550c /test-requirements.txt
parent266ee36d3387247f8cbc57327a71f86a181fd45f (diff)
downloadoslo-policy-82a792f201ca45b1043d46c744a24cd36b1580f5.tar.gz
Fix hacking min version to 3.0.1
flake8 new release 3.8.0 added new checks and gate pep8 job start failing. hacking 3.0.1 fix the pinning of flake8 to avoid bringing in a new version with new checks. Though it is fixed in latest hacking but 2.0 and 3.0 has cap for flake8 as <4.0.0 which mean flake8 new version 3.9.0 can also break the pep8 job if new check are added. To avoid similar gate break in future, we need to bump the hacking min version. - http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html Change-Id: I20e3db3b092462c85d784aad51d5e98f3499f3f1
Diffstat (limited to 'test-requirements.txt')
-rw-r--r--test-requirements.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/test-requirements.txt b/test-requirements.txt
index a7764af..fb0d03a 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.
-hacking>=3.0,<3.1.0 # Apache-2.0
+hacking>=3.0.1,<3.1.0 # Apache-2.0
oslotest>=3.2.0 # Apache-2.0
requests-mock>=1.2.0 # Apache-2.0
stestr>=2.0.0 # Apache-2.0