On 06/09/10 05:46, nik...@montao.com.br wrote:
Having used pylint to find trivial improvements like declaration overuse I try ask here more general for tips when or which developers should lint their code?
a) as Alexandre already wrote, constantly. :) In my case, that means pydev as I type + Hudson with pylint after each SVN commit.
b) to take the wind out of the sails of static typing evangelists that claim their compiler is the only way to catch typos (lint + unit tests are just as good).
_______________________________________________ Python-Projects mailing list Python-Projects@lists.logilab.org http://lists.logilab.org/mailman/listinfo/python-projects
