Home Original page

[Python-Dev] How is the GitHub workflow working for people?

Dan Stromberg drsalists at gmail.com
Wed Feb 21 22:03:12 EST 2018 
On Wed, Feb 21, 2018 at 2:19 PM, Barry Warsaw <barry at python.org> wrote:
> On Feb 21, 2018, at 13:22, Guido van Rossum <guido at python.org> wrote:
>>
>> I'm willing to reconsider if there's a good enough tool. Ditto for C code (or do we already do it for C?).
>
> For Python code, flake8 --possibly with our own custom plugins— is the way to go.

Is flake8 that much better than pylint, that pylint wouldn't even be discussed?

pylint does warn about some relatively unimportant things out of the
box, but it can be configured to ignore (almost?) everything it
checks.

I've been editing Python code in vim with syntastic.  I have syntastic
set up to run pyflakes, pycodestyle and pydocstyle.  And I have a
macro that saves the buffer, shells out and runs "make" with the
default rule - and that default rule almost always does a
whole-program pylint.

It's possible to make pylint check just one file from syntastic, but I
don't do that because it's too slow on large files.

I've gotten the impression that pylint can detect some errors that
pyflakes misses.  Not sure about flake8.

I do like it that flake8 has a mccabe check.  pylint doesn't appear to
have that, and instead relies on things like "too many statements",
"too many branches" and "too many variables".
More information about the Python-Dev mailing list