On Monday 06 September 2010 05:46:02 [email protected] wrote: > Hi > 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? I say parts of programming is done with paper and pencil more > like logic and algorithms we can't lint. So I suppose there's some kind of > "soft limit" to when lint is applicable both from a C and python > standpoint.
I say programming is done with a text editor. I use emacs, and set it so that it runs pylint in (almost) real time on my source code, using epylint and the elisp code distributed with pylint [1]. Pylint (and lint) won't catch algorithm errors. For these, I use unit testing extensively. [1] people using eclipse get similar benefits from pydev -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, CubicWeb, Debian : http://www.logilab.fr/formations Développement logiciel sur mesure : http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
