Lock bugbear version to prevent zuul failures

A new bugbear was released which broke zuul.
This commit locks bugbear at that release and
suppresses those two new error types.

Later commits may clean those up, however
it is more likely bugbear will be removed and
a different flake8 and hacking will be used.

Story: 2004515
Task: 30260
Change-Id: I213163b3043b439daccd1f9c9d6db846e1248dae
Signed-off-by: Al Bailey <Al.Bailey@windriver.com>
This commit is contained in:
Al Bailey 2019-03-29 09:00:17 -05:00
parent 497f93c7c7
commit 32d7999e90
1 changed files with 4 additions and 2 deletions

View File

@ -72,6 +72,8 @@ commands =
# B series are from bugbear
# B001 Do not use bare `except:
# B007 Loop control variable 'cpu' not used within the loop body.
# B009 Do not call getattr with a constant attribute value
# B010 Do not call setattr with a constant attribute value
# B301 Python 3 does not include `.iter*` methods on dictionaries.
# F series
# F401 'module' imported but unused
@ -79,7 +81,7 @@ ignore = E121,E123,E124,E125,E126,E127,E128,E265,E266,
E302,E303,E305,E402,E501,E722,E741,
H101,H102,H104,H201,H238,H237,H306,H401,H404,H405,
W191,W291,W391,W503,
B001,B007,B301,
B001,B007,B009,B010,B301,
F401
[testenv:pep8]
@ -88,7 +90,7 @@ usedevelop = False
skip_install = True
deps =
hacking
flake8-bugbear
flake8-bugbear<=19.3.0
flake8<3.6.0
commands =
flake8