98944bf7d6
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: I9bfb66c5e21ca3c1b81f84fbd46df7ce34d86378
17 lines
674 B
Plaintext
17 lines
674 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.
|
|
# Order matters to the pip dependency resolver, so sorting this file
|
|
# changes how packages are installed. New dependencies should be
|
|
# added in alphabetical order, however, some dependencies may need to
|
|
# be installed in a specific order.
|
|
#
|
|
# Hacking should appear first in case something else depends on pep8
|
|
hacking>=3.0.1,<3.1.0 # Apache-2.0
|
|
#
|
|
coverage!=4.4,>=4.0 # Apache-2.0
|
|
mock>=2.0.0 # BSD
|
|
nodeenv>=0.9.4 # BSD
|
|
pytest>=5.3.5 # MIT
|
|
testtools>=2.2.0 # MIT
|