Uh oh!
There was an error while loading. Please reload this page.
Replace flake8 with pylint - #280
Conversation
Some errored are currently disabled, just to get things going. We can then start removing those disabled errors by explicitly deciding on how to handle them.
jdufresne
commented
Jul 1, 2021
I think we should remove EOL Pythons. I've done so in PR #281. |
sethmlarson
commented
Jul 1, 2021
Isn't flake8 more complete than pylint? I've not seen projects moving from flake8 -> pylint, usually the other way. |
jdufresne
commented
Jul 1, 2021
FWIW, most projects I have worked on choose flake8 over pylint. So it is my personal choice as well. (But only that, personal) |
hartwork
commented
Jul 1, 2021
@nir0s what is the motivation behind choosing pylint over flake8? |
nir0s
commented
Jul 1, 2021
Yeah, I was making assumptions here. I personally moved away from flake8 in different projects because I felt like it has better reporting. However, I'm not strongly opinionated about this. |
nir0s
commented
Jul 1, 2021
I'm gonna close it. It's not worth a discussion AFAIC. |
.pylintrc