On Tue, Aug 18, 2015 at 3:00 PM, Claudiu Popa <pcmantic...@gmail.com> wrote: > Hello, > > > For quite some time, since the very first 'Forget the past' commit I have > access to, pylint had the ability of providing additional reports, such as > Global evaluation, Messages by category, Statistics by type etc. > For those of you who are unfamiliar with them, they look like this > http://paste.openstack.org/show/421040/ > pylint provides an easy way to disable them, by using the --reports > flag, as in `--reports=y|n`. > > After using pylint for some time, they're started to feel useless for me > and I'm always disabling them when running pylint.
Likewise. They are always the first thing I disable when setting up a pylint.rc file, and I am perpetually annoyed when I forget to include "-r n" when pylinting a one-off script via terminal. > They don't provide that much value, except maybe scaring new users > with all sorts of numbers, percentages and negative scores > (yes, the default formula allows the global evaluation > score to become negative). > > For pylint users, what do you think about the removal of these > reports from pylint? Yes please. Or at least make it default to disabled instead of enabled. > Would it cause problems for you? I guess removing the command-line option could break some build scripts, but the fix would be trivial and removing it would still definitely be a net win for me. > Are these reports in any sense useful for you? No. If I want an overview of or historical trends for pylint errors for a nontrivial project, I use Jenkins' Violations plugin, which doesn't rely on pylint's --report. Cheers, Chris -- http://chrisrebert.com _______________________________________________ code-quality mailing list code-quality@python.org https://mail.python.org/mailman/listinfo/code-quality
