767660b0a0
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: I4bf93e866b35bd5c7f584539760ff159a94c532b
20 lines
643 B
Plaintext
20 lines
643 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
|
|
fixtures>=3.0.0 # Apache-2.0/BSD
|
|
jsonschema>=3.2.0 # MIT
|
|
prometheus-client>=0.4.2 # Apache-2.0
|
|
oslo.config>=6.1.0 # Apache-2.0
|
|
oslotest>=3.2.0 # Apache-2.0
|
|
requests-mock>=1.2.0 # Apache-2.0
|
|
statsd>=3.3.0
|
|
stestr>=1.0.0 # Apache-2.0
|
|
testscenarios>=0.4 # Apache-2.0/BSD
|
|
testtools>=2.2.0 # MIT
|
|
doc8>=0.8.0 # Apache-2.0
|
|
Pygments>=2.2.0 # BSD license
|