6ff95efaf6
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: I1fe394ebd1f161eb73f53bfa17d2ccc860b9f51b
17 lines
553 B
Plaintext
17 lines
553 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.
|
|
|
|
coverage>=4.5.1 # Apache-2.0
|
|
doc8>=0.8.0 # Apache-2.0
|
|
freezegun>=0.3.10 # Apache-2.0
|
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
|
mock>=2.0.0 # BSD
|
|
oslotest>=3.3.0 # Apache-2.0
|
|
os-testr>=1.0.0 # Apache-2.0
|
|
testscenarios>=0.5.0 # Apache-2.0/BSD
|
|
testtools>=2.3.0 # MIT
|
|
stestr>=2.0.0 # Apache-2.0
|
|
os-api-ref>=1.4.0 # Apache-2.0
|
|
bandit>=1.6.0 # Apache-2.0
|