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: I0a0504f9ab35cf35fb02d4edf2564f23a278c5a2
This commit is contained in:
parent
6b5d1f45e9
commit
f1969109b1
@ -39,7 +39,7 @@ gitdb2==2.0.3
|
||||
GitPython==2.1.8
|
||||
google-api-python-client==1.4.2
|
||||
greenlet==0.4.10
|
||||
hacking==2.0.0
|
||||
hacking==3.0.1
|
||||
httplib2==0.9.1
|
||||
idna==2.6
|
||||
imagesize==1.0.0
|
||||
|
@ -3,7 +3,7 @@
|
||||
# process, which may cause wedges in the gate later.
|
||||
|
||||
# Install bounded pep8/pyflakes first, then let flake8 install
|
||||
hacking>=3.0,<3.1.0 # Apache-2.0
|
||||
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
||||
flake8-import-order # LGPLv3
|
||||
flake8-logging-format>=0.6.0 # Apache-2.0
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user