c6503b2c79
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: Ic3c5416af0a2a90847e32979d96ed3a531c2e498
18 lines
552 B
Plaintext
18 lines
552 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>=3.0.1,<3.1.0 # Apache-2.0
|
|
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
doc8>=0.6.0 # Apache-2.0
|
|
Pygments>=2.2.0 # BSD license
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
nose>=1.3.7 # LGPL
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
requests-mock>=1.2.0 # Apache-2.0
|
|
tempest>=17.1.0 # Apache-2.0
|
|
stestr>=2.0.0 # Apache-2.0
|
|
testtools>=2.2.0 # MIT
|
|
unittest2>=1.1.0 # BSD
|
|
|