a61c4bbe29
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: I4586bde1bd9f33dcdd803900bc648720073bdb62
22 lines
761 B
Plaintext
22 lines
761 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 already pins down pep8, pyflakes and flake8
|
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
|
bandit!=1.6.0,>=1.1.0 # Apache-2.0
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
kombu!=4.0.2,>=4.0.0 # BSD
|
|
PyMySQL>=0.7.6 # MIT License
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
psycopg2>=2.7 # LGPL/ZPL
|
|
stestr>=2.0.0 # Apache-2.0
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
testtools>=2.2.0 # MIT
|
|
testresources>=2.0.0 # Apache-2.0/BSD
|
|
doc8>=0.6.0 # Apache-2.0
|
|
Pygments>=2.2.0 # BSD license
|
|
# Next are used in integration tests only
|
|
tempest>=17.1.0 # Apache-2.0
|