Hi all, Last year I was taught a really good method of using pylint.
Instead of accepting a threshold like 8/10 or whatever... Set your continuous integration pipeline to fail a build if you don't get 10/10. (yes! you read it correctly!) Then, where you need to deviate from 'perfect style' - use an inline disable. eg. # pylint: disable=invalid-name Two advantages: - deviations from style end up clearly flagged in code-review / pull requests - it's not the fault of the one person who tips the score from 8.01 to 7.98 to fix a bunch of style errors Maybe this is common knowledge, maybe it's not. It was new for me - and I think it's really good practice, so I'm sharing it : ) Regards, Phil On Tuesday, 19 January 2016, Sylvain Thénault <sylvain.thena...@logilab.fr> wrote: > thank you, it's always nice to get such cheerful feedback. And congrat ! :) > > On 16 janvier 13:58, David Aguilar wrote: > > I just got git-cola[1] to 100% > > > > Your code has been rated at 10.00/10 (previous run: 10.00/10, +0.00) > > Wow ! Now this deserves our uttermost respect. > > Please send your code to python-proje...@logilab.org <javascript:;> > > > > Thanks for pylint! > > > > [1] https://github.com/git-cola/git-cola > > > > cheers, > > -- > > David > > -- > 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 > _______________________________________________ > Python-Projects mailing list > Python-Projects@lists.logilab.org <javascript:;> > https://lists.logilab.org/mailman/listinfo/python-projects
_______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org https://lists.logilab.org/mailman/listinfo/python-projects
