You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so I investigated this a bit because I was curious why I saw the behavior above - it turns out pylint does generally find more issues compared to pyflakes (what flake8 uses). What's happening is that pyflakes inspects the syntax tree of each source file separately, so it can't find issues across source files, e.g. like a call signature having the wrong number of arguments (i.e. if the function is imported from a different source file), but pylint can - albeit at the cost of speed.
Tbh given the above it might be worth actually using pylint more broadly in our repos in addition to flake8, so I'm gonna mark this one as pending close (not closing immediately to give others a chance to share thoughts)
Description
Do we getting anything additional from using pylint over flake8?
(Fwiw I got additional failures on #5298 on pylint compared to flake8)
The text was updated successfully, but these errors were encountered: