7213f7195e
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: I794bcf026f8c30d81c84b8c26e8b982b0e7b5b17
14 lines
495 B
Plaintext
14 lines
495 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.4,>=4.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
python-subunit>=1.0.0 # Apache-2.0/BSD
|
|
stestr>=2.0.0 # Apache-2.0
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
testtools>=2.2.0 # MIT
|
|
tempest>=17.1.0 # Apache-2.0
|