Just a general question: Since we do pylint for (some) test files as well, there has been a second pylint configuration file (pylintrc-test). Are there reasons why it is not updated at the same time as the main pylint configuration file? Do you also have a look at `make pylint-test`?
LGTM for this patch anyway, thanks, Thomas On Tue, Sep 24, 2013 at 4:26 PM, Michele Tartara <[email protected]>wrote: > In order to check for the correctness of the accesses to fields of objects, > pylint uses astng, but this is known to fail on some dynamically generated > classes. Still, newer pylint versions are stricter at performing this > check, and > therefore fail while testing our codebase. Disable the checking of a few > selected classes that incur in this problem. > > Signed-off-by: Michele Tartara <[email protected]> > --- > pylintrc | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/pylintrc b/pylintrc > index daea649..4fdec6e 100644 > --- a/pylintrc > +++ b/pylintrc > @@ -43,6 +43,7 @@ bad-functions = xrange > ignore-mixin-members = yes > zope = no > acquired-members = > +ignored-classes = sha1,md5,Popen,ChildProcess > > [VARIABLES] > init-import = no > -- > 1.7.10.4 > > -- Thomas Thrainer | Software Engineer | [email protected] | Google Germany GmbH Dienerstr. 12 80331 München Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Graham Law, Christine Elizabeth Flores
