After issue 598897 , stricter pylint checks are now enabled for new code in webkitpy, although existing code doesn't necessarily conform to new the checks. I made several changes in the past to start:
r392119
r392265
r393077
r397453
r397636
r400487
r408745
r410728
This issue could be considered "fixed" when lint-webkitpy comes up with no warnings for the whole codebase. Current issues can be listed by running the following command from the webkitpy directory:
pylint --rcfile=pylintrc $(find . -name "*.py" | grep -v thirdparty)
Comment 1 by bugdroid1@chromium.org
, Sep 6 2016