summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorzhoulinhui <df.some@foxmail.com>2020-09-18 00:26:35 +0800
committerzhoulinhui <df.some@foxmail.com>2020-09-18 00:26:46 +0800
commita2b52b1309026749940142c1b9a39ae23aeeff9e (patch)
treec77f297f0036bf322f6ff279e95b814e0e1ccab6
parent128a747332494e674d95235483976046fbd53a5c (diff)
downloadoslo-serialization-a2b52b1309026749940142c1b9a39ae23aeeff9e.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: Idc5d70e753953aeb006caeb3ba8f78f5ceeafdf3
-rw-r--r--test-requirements.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/test-requirements.txt b/test-requirements.txt
index 5dd6fe0..b7fbcb9 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
netaddr>=0.7.18 # BSD
stestr>=2.0.0 # Apache-2.0