From 11b026969612b2aec6b91aaed131c762951ff428 Mon Sep 17 00:00:00 2001 From: Gilles Peskine Date: Tue, 24 Mar 2020 18:47:06 +0100 Subject: [PATCH] Pylint: silence locally-disabled/enabled messages If we disable or enable a message locally, it's by design. There's no need to clutter the Pylint output with this information. Signed-off-by: Gilles Peskine --- .pylintrc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.pylintrc b/.pylintrc index 262b5cf04..08c114ad9 100644 --- a/.pylintrc +++ b/.pylintrc @@ -40,6 +40,9 @@ max-attributes=15 max-module-lines=2000 [MESSAGES CONTROL] +# * locally-disabled, locally-enabled: If we disable or enable a message +# locally, it's by design. There's no need to clutter the Pylint output +# with this information. # * logging-format-interpolation: Pylint warns about things like # ``log.info('...'.format(...))``. It insists on ``log.info('...', ...)``. # This is of minor utility (mainly a performance gain when there are @@ -57,7 +60,7 @@ max-module-lines=2000 # return value2 # * unnecessary-pass: If we take the trouble of adding a line with "pass", # it's because we think the code is clearer that way. -disable=logging-format-interpolation,no-else-return,unnecessary-pass +disable=locally-disabled,locally-enabled,logging-format-interpolation,no-else-return,unnecessary-pass [REPORTS] # Don't diplay statistics. Just the facts.