296c8669a9
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: Idb45c6b09980c6850b1acf05a03c9be59fb254bc
22 lines
727 B
Plaintext
22 lines
727 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
|
|
ddt>=1.0.1 # MIT
|
|
doc8>=0.6.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
PyMySQL>=0.7.6 # MIT License
|
|
iso8601>=0.1.11 # MIT
|
|
oslo.reports>=1.18.0 # Apache-2.0
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
stestr>=1.0.0 # Apache-2.0
|
|
psycopg2>=2.7.3 # LGPL/ZPL
|
|
testtools>=2.2.0 # MIT
|
|
WebTest>=2.0.27 # MIT
|
|
bashate>=0.5.1 # Apache-2.0
|
|
pycodestyle>=2.0.0,<2.6.0 # MIT
|
|
flake8-import-order>=0.17.1 # LGPLv3
|
|
Pygments>=2.2.0 # BSD
|
|
bandit!=1.6.0,>=1.1.0,<2.0.0 # Apache-2.0
|