Bump hacking min version to 3.0.1

Code Issues Proposed changes

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: Iff96a7a4c8f2a0f625a47ac44158d904fa132157

This commit is contained in:

zhangbailin

2020年05月18日 08:42:19 +08:00

committed by Brin Zhang

parent 00ad03b709

commit c1c093fc2e

2 changed files with 2 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

2
lower-constraints.txt

View File

@@ -20,7 +20,7 @@ future==0.16.0

gitdb==4.0.4

GitPython==3.1.1

greenlet==0.4.13

hacking==3.0.0

hacking==3.0.1

ifaddr==0.1.6

imagesize==1.0.0

ironic-lib==4.1.0

2
test-requirements.txt

View File

@@ -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.0,<3.1.0 # Apache-2.0

hacking>=3.0.1,<3.1.0 # Apache-2.0

coverage!=4.4,>=4.0 # Apache-2.0

testtools>=2.2.0 # MIT

oslotest>=3.2.0 # Apache-2.0