a14c2d9b1a
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: Id086fbfefa941aa87db5f2b105e559265208b225
17 lines
693 B
Plaintext
17 lines
693 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.
|
|
|
|
# Keep hacking first, it pulls in the right versions of flake8, mccabe and pyflakes
|
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
|
bashate>=0.5.1 # Apache-2.0
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
mock>=2.0.0 # BSD
|
|
virtualenv>=14.0.6 # MIT
|
|
# TODO(noonedeadpunk) Upgrade linters versions and drop pycodestyle
|
|
# once we stop doing linters check for the integrated repo with
|
|
# openstack-ansible-tests/test-ansible-lint.sh
|
|
flake8<2.6.0,>=2.5.4 # MIT
|
|
ansible-lint==3.4.21 # MIT
|
|
pycodestyle>=2.5.0,<2.6.0
|