summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGhanshyam Mann <gmann@ghanshyammann.com>2020-05-12 19:47:38 -0500
committerGhanshyam Mann <gmann@ghanshyammann.com>2020-05-18 18:46:26 +0000
commite5280f282b4445ba9d72c212818651a8620925b4 (patch)
tree57ff346c8ea080e8c17b4c27135fbf98a6278ff3
parentc4059900c5be01b1da87ea8143aff7498eea2eaf (diff)
downloadpython-neutronclient-e5280f282b4445ba9d72c212818651a8620925b4.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: I5486638526b26ce0710c7b1926e408dd70057a66 (cherry picked from commit 6d9d2e62915edcf6a5796984012ce17e1d87f1c5)
-rw-r--r--test-requirements.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/test-requirements.txt b/test-requirements.txt
index a1eb9b1..a0d76ed 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>=1.1.0 # Apache-2.0
+hacking>=3.0.1,<3.1.0 # Apache-2.0
bandit!=1.6.0,>=1.1.0 # Apache-2.0
coverage!=4.4,>=4.0 # Apache-2.0