Skip to content
Snippets Groups Projects

Resolve "Use pylint for linting"

Merged James Ennis requested to merge jennis/buildstream:239-use-pylint-for-linting into master

Closes #239 (closed)

Linted through the code base and made small changes to various parts of the project.

NOTE: There are still some pylint warning messages disabled, this is either because:

  1. No obvious changes could be made to "improve" the standard of the code, or
  2. The changes that were made to address this message lead to build errors.

Using pylint

To lint the codebase run ./setup.py test --addopts '--pylint -m pylint'

  • This will provide warnings when the linter comes across a potential error or style issue. They are generally relatively easy to fix/change.
  • Please note that some warnings have been permanently disabled in the .pylintrc configuration file
  • If the warning for a line of code is irrelevant disable it using: # pylint: disable=<warning-name>
Edited by James Ennis

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • I don't understand how "minor modifications to buildstream/_pipeline.py" is related to linting, or why the changes to the format string in the previous commit aren't squashed into it.

  • "disabled global-statement warnings where necessary and rectified import orders" would be better as two different commits.

  • richardmaw-codethink
  • richardmaw-codethink
  • It's bad form to do more than one change per commit. "pylint: cleaned up some whitespace warnings and disabled cyclic-import" should at minimum split the whitespace changes from the cyclic-import.

    Since a lot of the changes to whitespace made were things introduced earlier in the series, the whitespace changes should be split up then squashed into those commits.

  • "cleaned up commit messages" is mis-titled, since that's not a thing you can do with a commit, and it's removing junk files which were added earlier, which should be squashed into the commit which added it in the first place.

  • richardmaw-codethink
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Please register or sign in to reply
    Loading