From b993b5f43b17459963fda103623686ad8f8914a5 Mon Sep 17 00:00:00 2001 From: Ghanshyam Mann Date: Tue, 12 May 2020 20:02:04 -0500 Subject: [PATCH] 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. Also removing the hacking and other related dep from lower-constraints file as theose are blacklisted requirements and does not need to be present there. - http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html Change-Id: I861f3305af18d112d51a1dc368a00e5fe763b788 --- lower-constraints.txt | 1 - test-requirements.txt | 2 +- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/lower-constraints.txt b/lower-constraints.txt index 68fa740..54d1629 100644 --- a/lower-constraints.txt +++ b/lower-constraints.txt @@ -1,7 +1,6 @@ bandit==1.4.0 coverage==4.0 doc8==0.6.0 -hacking==0.12.0 oslo.i18n==3.15.3 oslo.serialization==2.28.1 oslo.utils==3.33.0 diff --git a/test-requirements.txt b/test-requirements.txt index f417486..975c581 100644 --- a/test-requirements.txt +++ b/test-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. -hacking>=3.0,<3.1.0 # Apache-2.0 +hacking>=3.0.1,<3.1.0 # Apache-2.0 bandit>=1.1.0 # Apache-2.0 coverage>=4.0,!=4.4 # Apache-2.0