
The 2.6.0 version introduces some checks that cause failures with the current code. To avoid that, cap pycodestyle to a version that had been tested without errors. In Rocky we already had tests with pycodestyle, but proper listing in test-requirements.txt was only added in I33be4f5d4ae48c6bd48d80e3f1185ef8307a2a0c Conflicts: test-requirements.txt Change-Id: I00a35884b14af3e2cf751c04312c847ecfe658c7 (cherry picked from commit 719cae183ae3f67da3ac834140af3f85f2113c10)
25 lines
810 B
Plaintext
25 lines
810 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>=1.1.0,<1.2.0 # Apache-2.0
|
|
|
|
bandit>=1.1.0,<1.5.0 # Apache-2.0
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
flake8-import-order==0.12 # LGPLv3
|
|
pycodestyle>=2.0.0,<2.6.0 # MIT
|
|
mock>=2.0.0 # BSD
|
|
python-subunit>=1.0.0 # Apache-2.0/BSD
|
|
testtools>=2.2.0 # MIT
|
|
testresources>=2.0.0 # Apache-2.0/BSD
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
WebTest>=2.0.27 # MIT
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
stestr>=1.0.0 # Apache-2.0
|
|
reno>=2.5.0 # Apache-2.0
|
|
ddt>=1.0.1 # MIT
|
|
pylint==1.4.5 # GPLv2
|
|
# Needed to run DB commands in virtualenvs
|
|
PyMySQL>=0.7.6 # MIT License
|
|
bashate>=0.5.1 # Apache-2.0
|