Skip to content

Commit

Permalink
Disable pylint warnings about missing open() encoding parameter.
Browse files Browse the repository at this point in the history
The new version of pylint adds a new warning that warns about not
specifying encoding when opening a file. This option was introduced
mostly to support better compatibility when running Python packages on
Windows, where the usage of the implicit encoding causes trouble.

Also adding two stylistic options to the disabled ones: use-dict-literal
and use-list-literal, both suggesting to use []/{} instead of calling
list() or dict().
  • Loading branch information
MichalHe authored and pirat89 committed Aug 23, 2021
1 parent fcb033f commit 305668f
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions .pylintrc
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ disable=
unsubscriptable-object,
unused-argument,
unused-import,
unspecified-encoding,
# "C" Coding convention violations
bad-continuation,
missing-docstring,
Expand All @@ -37,6 +38,8 @@ disable=
too-many-locals,
too-many-statements,
consider-using-from-import,
use-list-literal,
use-dict-literal,
# new for python3 version of pylint
useless-object-inheritance,
consider-using-set-comprehension, # pylint3 force to use comprehension in place we don't want (py2 doesnt have these options, for inline skip)
Expand Down

0 comments on commit 305668f

Please sign in to comment.