2ce01bf14e
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 Trivial change Change-Id: I7728b8f6e8dc93c6494b69ad1eb1ee99c79a6f78
23 lines
718 B
Plaintext
23 lines
718 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
|
|
# remove this pyflakes from here once you bump the
|
|
# hacking to 3.2.0 or above. hacking 3.2.0 takes
|
|
# care of pyflakes version compatibilty.
|
|
pyflakes>=2.1.1
|
|
|
|
coverage>=3.6
|
|
ddt>=0.7.0
|
|
python-subunit>=0.0.18
|
|
selenium>=2.50.1 # Apache-2.0
|
|
sphinx>=2.0.0,!=2.1.0 # BSD
|
|
openstackdocstheme>=2.2.1 # Apache-2.0
|
|
testrepository>=0.0.18
|
|
testscenarios>=0.4
|
|
testtools>=1.4.0
|
|
# This also needs xvfb library installed on your OS
|
|
xvfbwrapper>=0.1.3 #license: MIT
|
|
reno>=3.1.0 # Apache-2.0
|