[checkmk-commits] Classify bare-except and broad-except warnings.

Module: check_mk Branch: master Commit: 5376d4525e9e9c7c61dd97e34e34ccebc3a7bbdd URL: http://git.mathias-kettner.de/git/?p=check_mk.git;a=commit;h=5376d4525e9e9c… Author: Sven Panne <sp(a)mathias-kettner.de> Date: Thu Jul 19 14:53:40 2018 +0200 Classify bare-except and broad-except warnings. Change-Id: Idb648f2122d46dbaa9d103994c524ab1396812a8 --- tests/pylint/pylintrc | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/tests/pylint/pylintrc b/tests/pylint/pylintrc index bceb6de..9f26a30 100644 --- a/tests/pylint/pylintrc +++ b/tests/pylint/pylintrc @@ -12,8 +12,6 @@ persistent=yes [MESSAGES CONTROL] disable= - bare-except, - broad-except, cell-var-from-loop, consider-iterating-dictionary, consider-using-enumerate, @@ -83,6 +81,11 @@ disable= # duplication (introduce new classes, combine methods, etc.) attribute-defined-outside-init, #--------------------------------------------------------------------------- + # Enabling these warnings would be nice, they are mostly a sign of sloppy + # programming practice. In some cases, they can even hide bugs. + bare-except, + broad-except, + #--------------------------------------------------------------------------- # Enabling this would be nice, but not crucial. At the moment, we have quite # a few violations, so we postpone fixing this. When we do it eventually, we # probably want to use "include-naming-hint=yes" in the BASIC section.