On 12/22/14 10:37 AM, Skip Montanaro wrote:
* Couldn't you just run pylint on the subset of files which have changed?
BTW, diff-cover (https://github.com/edx/diff-cover) is a tool that runs
pylint, pep8, and coverage on just your recent changes, rather than on
the entire working tree resulting from your changes. This gives you an
achievable goal (each patch should be clean) that can help move a messy
project toward goodness in a satisfying way.
--Ned.
_______________________________________________
code-quality mailing list
code-quality@python.org
https://mail.python.org/mailman/listinfo/code-quality
