dbda8ecbe3
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: Iad2e2f56e4cd71f371c760eef85cb121ef1438fe
25 lines
755 B
Plaintext
25 lines
755 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 should appear first in case something else depends on pep8
|
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
|
pyflakes>=2.1.1
|
|
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
pykmip>=0.7.0 # Apache 2.0 License
|
|
stestr>=2.0.0 # Apache-2.0
|
|
testtools>=2.2.0 # MIT
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
requests>=2.18.0 # Apache-2.0
|
|
WebTest>=2.0.27 # MIT
|
|
python-keystoneclient>=3.8.0 # Apache-2.0
|
|
tempest>=17.1.0 # Apache-2.0
|
|
|
|
# Bandit build requirements
|
|
bandit!=1.6.0,>=1.1.0 # Apache-2.0
|
|
|
|
doc8>=0.6.0 # Apache-2.0
|
|
Pygments>=2.2.0 # BSD license
|