What I mean is: can I configure pylint in a way that it report *all* pep8 violations (among others)? E.g. I want to use only one linter -- pylint -- and I want to make sure the code is fully pep8 compliant. Demetrio On Tue, Mar 3, 2020 at 1:58 PM Ian Stapleton Cordasco < graffatcolmingov@gmail.com> wrote:

Your question sounds simple, but I do not understand what you mean by "covers"

Sent from my phone with my typo-happy thumbs. Please excuse my brevity

On Tue, Mar 3, 2020, 06:37 Demetrio Rodriguez Tereshkin < demetrio.rodriguez-tereshkin@sclable.com> wrote:

...

Dear PyCQA,

I have a very simple question to which I am unable to find a simple an clear answer: *Does pylint fully cover pep8?*

Thank you in advance for clarifying!

Best, Demetrio

*--*

*Demetrio Rodriguez Tereshkin* Machine Learning Engineer

+43 664 4846744 <+436644846744> demetrio.rodriguez.tereshkin@sclable.com

*Sclable Business Solutions GmbH* Marc-Aurel-Straße 10-12/Top 10, 1010 Vienna, Austria https://sclable.com

Company Registration Number: FN 387162g Commercial Register Court: Commercial Court of Vienna _______________________________________________ code-quality mailing list -- code-quality@python.org To unsubscribe send an email to code-quality-leave@python.org https://mail.python.org/mailman3/lists/code-quality.python.org/

On 3/5/20 8:34 AM, Ian Stapleton Cordasco wrote:

I'm fairly certain that: ... So, my understanding is that no, you can not use only one linter.

Let me express a counter opinion (and that's all they are, opinions) PEP 8 presents Guidelines, it is not the ultimate arbiter of what code should and should not look like. "Fully covering PEP8" has no real meaning. In fact, read the PEP itself for comments on that. Decide what things you think matter to your project(s), see if you can configure (for example) Pylint to report that way, distribute that consfiguration (that is, check it in as part of the codebase), and then use that as a tool to evaluate code. If you can, there's no particular need to require multiple static code checkers. Static code checking is only a small part of the puzzle of code quality anyway, best not to get completely hung up on it.