mirror of
https://github.com/certbot/certbot.git
synced 2026-06-04 22:33:00 -04:00
make pylint happy
This was taken from https://github.com/certbot/certbot/pull/9073.
This commit is contained in:
parent
4b488e5068
commit
f029746960
1 changed files with 3 additions and 1 deletions
|
|
@ -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]
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue