aee87c8e14
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. Also removing the hacking and other related dep from lower-constraints file as theose are blacklisted requirements and does not need to be present there. - http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014828.html Change-Id: Id693765fa9216f880d7105bbac3cd60f2db8500c
15 lines
478 B
Plaintext
15 lines
478 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 pins flake8 etc
|
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
|
coverage>=4.0
|
|
mock>=2.0.0
|
|
pylint==2.4.0 # GPLv2
|
|
stestr>=2.0.0 # Apache-2.0
|
|
testtools>=2.2.0
|
|
sphinx!=1.6.6,!=1.6.7,!=2.1.0,>=1.6.2 # BSD
|
|
openstackdocstheme>=1.31.2 # Apache-2.0
|
|
sphinxcontrib-apidoc>=0.2.0
|