774bc9264b
The 2.6.0 version introduces some checks that cause failures with the current code. hacking and flake8 cap could have solve the pycodestyle compatible version but flake8-import-order which does not cap the pycodestyle pulled its latest version and break things. Also remove the flake8 from test-requirements and let hacking handle the flake8 version otherwise ironic will still pull the latest flake8 which can break things in future. To make it work, we need to explicitly cap pycodestyle itself so that no other package pull the new checks in. Change-Id: Ia4b6f5aa8fe45d08a1563160e585947f35501ef2
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.0,<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
|