keyword: pylint errors

[Benoit Boissinot]

On Tue, Feb 9, 2010 at 2:09 AM, Christian Ebert <blacktrash at gmx.net> wrote:
> Hi,
>
> I'm aiming pylint at the keyword extension without knowing what I
> am doing ;-) So some informed pointers/help would be great.
>
> $ pylint -e keyword.py

First note that a recent pylint (from last december) is much more
useful. They had a sprint back then and fixed lots of stuff.

Then I usually do that:
pylint --rcfile contrib/pylintrc hgext.keywork

> Exception RuntimeError: 'maximum recursion depth exceeded while calling a Python object' in <type 'exceptions.RuntimeError'> ignored
> Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in <type 'exceptions.AttributeError'> ignored
> Exception RuntimeError: 'maximum recursion depth exceeded in __subclasscheck__' in <type 'exceptions.AttributeError'> ignored
> ************* Module keyword
> E1101:472:reposetup.kwrepo.file: Instance of 'kwrepo' has no 'sopener' member
> E1002:474:reposetup.kwrepo.wread: Use super on an old style class
> E1002:478:reposetup.kwrepo.commit: Use super on an old style class
> E1002:487:reposetup.kwrepo.kwcommitctx: Use super on an old style class
> E1101:490:reposetup.kwrepo.kwcommitctx: Instance of 'kwrepo' has no 'wlock' member
> E1101:491:reposetup.kwrepo.kwcommitctx: Instance of 'kwrepo' has no 'lock' member
> E1101:509:reposetup.kwrepo.kwcommitctx: Instance of 'kwrepo' has no 'hook' member
>
>
> Let's put the RuntimeError aside, at least for the moment. Now,
> with the following change:
>

Ignore this error, it's pylint not detecting the parent class (maybe
I'll add the error to the blacklist).
>
> P.S. Why does pylint deprecate the builtin map() function?

because [foo(x) for x in stuff] is more pythonic. But we could
desactivate the warning.

regards,

Benoit