pylint support about esmvaltool

[bouweandela]

It would be nice to recommend pylint in the developer documentation, e.g. in section "7.5 Coding rules and standards" instead of (or next to) pyflakes and to start using it ourselves of course.

See for example this blog on why pylint is the best tool for static code analysis:
https://blog.codacy.com/review-of-python-static-analysis-tools-ff8e7e27f972

Is there some way in which I can edit the documentation?

[bouweandela]

Codacy uses prospector, a tool which tries to intelligently combine the output of various Python linters of which pylint is the most comprehensive. We could also recommend prospector instead, probably with a recommended level of strictness, to help get a quick check if your code is any good according to Codacy before committing.

[nielsdrost]

Could we also add a prospector check to the setup.py, so I could run "python setup.py check" or something?

[bouweandela]

Sure, I could add a command ./setup.py lint that does that? check is already taken.

[nielsdrost]

Sounds good, thanks!