850710c46f
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: I931ffdb03ea55047439d019ccb8a1493b56f2569
19 lines
687 B
Plaintext
19 lines
687 B
Plaintext
# 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 already pins down pep8, pyflakes and flake8
|
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
|
bandit!=1.6.0,>=1.1.0 # Apache-2.0
|
|
Babel!=2.4.0,>=2.3.4 # BSD
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
httplib2>=0.9.1 # MIT
|
|
oslo.context>=2.19.2 # Apache-2.0
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
stestr>=1.0.0 # Apache-2.0
|
|
requests-mock>=1.2.0 # Apache-2.0
|
|
testrepository>=0.0.18 # Apache-2.0/BSD
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
testtools>=2.2.0 # MIT
|
|
docutils>=0.11
|