summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGhanshyam Mann <gmann@ghanshyammann.com>2020-05-12 21:23:27 -0500
committerGhanshyam Mann <gmann@ghanshyammann.com>2020-05-15 10:49:51 -0500
commit952d2892e2e3dc0a3716787a75125fc467b8541a (patch)
treec9c546438aeda979a73bc05c8a8cb365fbd67432
parentb9d65b624971329ad81fbc0fe23b2bbc3b0edf39 (diff)
downloadpython-troveclient-952d2892e2e3dc0a3716787a75125fc467b8541a.tar.gz
Fix hacking min version to 3.0.1
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: Icad3221eddcc5f4e3b17f7d11266d938d1ea6201
-rw-r--r--lower-constraints.txt4
-rw-r--r--test-requirements.txt2
2 files changed, 1 insertions, 5 deletions
diff --git a/lower-constraints.txt b/lower-constraints.txt
index 6c920e5..eaa72be 100644
--- a/lower-constraints.txt
+++ b/lower-constraints.txt
@@ -15,8 +15,6 @@ dogpile.cache==0.6.2
dulwich==0.15.0
extras==1.0.0
fixtures==3.0.0
-flake8==2.5.5
-hacking==0.12.0
httplib2==0.9.1
idna==2.6
imagesize==0.7.1
@@ -48,11 +46,9 @@ oslo.serialization==2.18.0
oslo.utils==3.33.0
oslotest==3.2.0
pbr==2.0.0
-pep8==1.5.7
positional==1.2.1
prettytable==0.7.2
pycparser==2.18
-pyflakes==0.8.1
Pygments==2.2.0
pyOpenSSL==17.1.0
pyparsing==2.1.0
diff --git a/test-requirements.txt b/test-requirements.txt
index 689537c..f3170af 100644
--- a/test-requirements.txt
+++ b/test-requirements.txt
@@ -1,7 +1,7 @@
# 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,<3.1.0 # Apache-2.0
+hacking>=3.0.1,<3.1.0 # Apache-2.0
coverage!=4.4,>=4.0 # Apache-2.0
fixtures>=3.0.0 # Apache-2.0/BSD
oslotest>=3.2.0 # Apache-2.0