On 18 août 20:35, Skip Montanaro wrote:
> On Tue, Aug 18, 2015 at 5:00 PM, Claudiu Popa <pcmantic...@gmail.com> wrote:
>
> > 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?
> >
>
> No problem removing them.
> Not really useful in my experience, except very rarely as a relative
> indicator of the direction things are moving.
>
> As a corollary, I will note that some users where I work seemed mesmerized
> by high scores (10/10, etc) and relied on them, not being aware that pylint
> wasn't some all-seeing-all-knowing Python code genie. I tried to disabuse
> them of that notion. I think it would be better to remove them and make
> people (especially Python newbies) focus on individual messages.
though that's a point advanced python/pylint users shouldn't ignore. In my
experience, the score mecanism of pylint has catched a lot of new comers'
attention and, as Skip mentioned, magnetized most of them through the wish of
getting an higher score. This is also useful for "smoke test" in CI tools
("pylint score must be greater than 8").
So while a agree most other reports could be disabled by default, and probably
simply dropped, I wish to keep this distinguishing feature, and even think it
should still be activated by default.
--
Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.62.17.16.42)
Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations
Développement logiciel sur mesure: http://www.logilab.fr/services
CubicWeb, the semantic web framework: http://www.cubicweb.org
_______________________________________________
code-quality mailing list
code-quality@python.org
https://mail.python.org/mailman/listinfo/code-quality
