On 3/18/14 6:27 PM, Anne Mulhern wrote:
Hi!
This is a question about making your favorite VCS and pylint interact.
The idea is that sometimes there's a project and you're running pylint on it,
but you want to distinguish among two kinds of errors:
1) Errors introduced by the last few commits.
2) Errors that have been around forever and that are not the committers
responsibility to fix.
If you have a lot of errors of type (2) you don't want the committer to have to
wade through them looking for any errors they might
have introduced.
(Of course, there is a very hard working person in the background who is
constantly working on addressing the many errors of type (2)).
So, it is easy to automate running pylint on a tree that includes the last few
commits (as specified by the user) and also
on a tree that is missing the last few commits.
The problem is diffing the results from running pylint on these two different
trees.
I see that the pylint results are dumped in pickle format into a pylint.d
directory. Presumably it is from that info that
the textual reports are extracted and displayed, though I am not certain.
I can see that something similar has been proposed before:
http://www.logilab.org/ticket/20386.
However, the difference is that I assume two pylint.d directories, one for each
source tree, and I'm interested in comparing them, somehow.
It is not sufficient to do an exact compare, as line numbers and so forth may
be changed.
I'ld welcome suggestions or if anybody has knowledge of any existing utility
that does this that would be great.
At edX, we wrote a tool called diff-cover that produces differential
coverage reports, and also pylint and pep8 reports. It lets the
developer focus on the effect of the changes they are making, rather
than on the entire working tree: https://github.com/edx/diff-cover
--Ned.
Thanks!
- mulhern
_______________________________________________
code-quality mailing list
code-quality@python.org
https://mail.python.org/mailman/listinfo/code-quality
_______________________________________________
code-quality mailing list
code-quality@python.org
https://mail.python.org/mailman/listinfo/code-quality
