[code-quality] Pylint reports, is anyone using them?

[Jeff Quast]

As a long time pylint user, certainly have seen this before, never found it particularly useful. In retrospect, a bit of a time waster for the consumer, too!

When a novice discovers this feature, they may be misdirected to attempt to make use of it, when independent aggregation and reporting tools that integrate with your VCS or CI are so much more comprehensive.

the 'coverage' tool forgoes all this complexity of reporting, yet http://coveralls.io — possibly written in another language all together — performs all such functions perfectly fine.

jq

> On Aug 18, 2015, at 3:00 PM, Claudiu Popa <pcmanticore at 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.
> 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? Would it cause problems for you?
> Are these reports in any sense useful for you?
> 
> If there's no negative push-back, we'll go through the normal deprecation
> procedures, so they won't be removed until two releases for now
> or until Pylint 2.0. As a benefit, we'll get rid of a lot of code that no one
> is happy to maintain and the maintainers can focus on developing
> the analysis capabilities instead.
> 
> 
> Thank you,
> Claudiu
> _______________________________________________
> code-quality mailing list
> code-quality at python.org
> https://mail.python.org/mailman/listinfo/code-quality