Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add flake8 checking on travis #2340

Merged
merged 4 commits into from
Feb 14, 2018
Merged

Add flake8 checking on travis #2340

merged 4 commits into from
Feb 14, 2018

Conversation

philippjfr
Copy link
Member

Adds this line to the travis.yml:

flake8 --ignore=E,W,F999,F405 holoviews tests

Also fixes all current flake issues, fixing two undefined variable bugs in the process. In another PR we should clean up the install and consider moving some of the code out into scripts so we can clean up a bit and start using separate build stages for linting, tests and eventually package building.

@philippjfr philippjfr changed the title Pyflakes Add flake8 checking on travis Feb 14, 2018
@philippjfr philippjfr mentioned this pull request Feb 14, 2018
@jlstevens
Copy link
Contributor

There are a number of flakes I am in favour of detecting and raising as errors:

  • Unreferenced variables
  • Unused variables
  • Unused imports

These typically do indicate errors or sensible ways the code should be simplified and cleaned up. I am strongly opposed to having other types of flakes, such as those to do with formatting or style issues being raised as errors on Travis.

I just want to be clear about this and I will not consider having other types of flakes being raised as errors unless someone can make a very compelling case. As this PR does only raise errors for the key flake types listed above, I am happy to merge.

@jlstevens jlstevens merged commit 585d732 into master Feb 14, 2018
@jbednar
Copy link
Member

jbednar commented Feb 14, 2018

It would be nice if a github PR could have a friendly little button that one could click on to get warnings, i.e. things that shouldn't break the build but are possibly of interest or worth dealing with. Right now it's a strict binary decision; if it doesn't break the build, we will basically never see anything about it. :-(

philippjfr added a commit that referenced this pull request Feb 14, 2018
@jlstevens
Copy link
Contributor

@jbednar That would be a lovely Github feature to have indeed!

@philippjfr philippjfr deleted the pyflakes branch February 16, 2018 12:55
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 25, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants