Why Pylint Is Both Useful and Unusable, and How You Can Actually Use It
&gt; The real problem is the amount of output.<p>That&#x27;s a nonsense argument.  The output is proportional to the number of violations.  If you keep your project clean, then you&#x27;ll have about a report of about 100 lines showing the statistics, with a one-line message: &quot;your code has been rated at 10&#x2F;10&quot; at the end.<p>Of course, if you run it against a project that is full of violations, you&#x27;ll get lots of violation messages.  If you use a linter or style checker or whatever on a project that is full of violations, and it doesn&#x27;t produce lots of output, then the tool is rubbish.<p>The right thing to do is to use it from the start and either fix or explicitly ignore any violations as they come up.<p>The approach described in this blog post is good for existing projects.  However, the linked examples disable all warnings and explicitly enable those that the author has deemed important.  It would be better to explicitly disable unimportant ones.