From f029746960a61f9bbf211ede5602eff0139ce67a Mon Sep 17 00:00:00 2001 From: Brad Warren Date: Mon, 22 Nov 2021 17:02:14 -0800 Subject: [PATCH] make pylint happy This was taken from https://github.com/certbot/certbot/pull/9073. --- .pylintrc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.pylintrc b/.pylintrc index ccd660239..d2730018d 100644 --- a/.pylintrc +++ b/.pylintrc @@ -72,7 +72,9 @@ extension-pkg-whitelist=pywintypes,win32api,win32file,win32security # (unspecified encoding makes the open function use the default encoding of the system) # than a clear flaw on which a check should be enforced. Anyway the project does # not need to enforce encoding on files so we disable this check. -disable=fixme,locally-disabled,locally-enabled,bad-continuation,no-self-use,invalid-name,cyclic-import,duplicate-code,design,import-outside-toplevel,useless-object-inheritance,unsubscriptable-object,no-value-for-parameter,no-else-return,no-else-raise,no-else-break,no-else-continue,raise-missing-from,wrong-import-order,unspecified-encoding +# 7) consider-using-f-string is "suggesting" to move to f-string when possible with an error. This +# clearly relates to code design and not to potential defects in the code, let's just ignore that. +disable=fixme,locally-disabled,locally-enabled,bad-continuation,no-self-use,invalid-name,cyclic-import,duplicate-code,design,import-outside-toplevel,useless-object-inheritance,unsubscriptable-object,no-value-for-parameter,no-else-return,no-else-raise,no-else-break,no-else-continue,raise-missing-from,wrong-import-order,unspecified-encoding,consider-using-f-string [REPORTS]