-
Notifications
You must be signed in to change notification settings - Fork 3
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run flake8 on CI #44
Run flake8 on CI #44
Conversation
To make sure our fixes stay and the code stays clean going forward, we need to start running flake8 during CI. In order to make that happen, we first need to install flake8 when running CI. Hence we add a version of flake8 here that should be installable on all Python versions that we support.
Drop filler comment from cookiecutter template and add a comment above where are test suite is run.
To make sure our code quality remains ok, start running flake8 as part of our CI. If the flake8 run fails, the build will be failed as well. Should help us catch code quality errors before they creep into the codebase.
- coverage erase | ||
- coverage run --source . setup.py test | ||
- coverage report -m | ||
|
||
# Do some basic linting of the code. | ||
- flake8 . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This runs on all of our code including the library, the tests, and our setup.py
file.
@@ -9,6 +9,7 @@ dependencies: | |||
- coverage==4.0.3 | |||
- python-coveralls==2.7.0 | |||
- pytest==3.0.5 | |||
- flake8==3.2.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pinned to this version as packages exists on Python 2.7, 3.4, 3.5, and 3.6 from conda-forge
.
Testing that this works as intended in PR ( #45 ). |
Start running flake8 as part of all CI builds. Make sure flake8 is added and version fixed in our CI requirements as well. Should help make sure the code quality here remains ok (especially since we have fixed some issues 馃槈).