On 17 mars 10:58, Maarten ter Huurne wrote: > On Wednesday 17 March 2010, Mads Kiilerich wrote: > > > It seems like pylint have different goals with different focus and > > emphasis. > > > > The man page says: > > pylint - python code static checker
this is "pylint -e", and should probably be fixed/enhanced to match the reality. > > pylint --help says: > > Check that a module satisfy a coding standard (and more !). this should be also fixed to match bare "pylint". [snip] Mads, are you ok that pylint -e does what you expect? I agree with the following points: * we should probably disable statistical reports by default * it should be easy to enable/disable messages by ids or by categories or by checker. All of this is possible today but with different options. We could probably simply have --enable/--disable and let pylint be smarter to handle them. -- Sylvain Thénault LOGILAB, Paris (France) 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 http://lists.logilab.org/mailman/listinfo/python-projects
