-
Notifications
You must be signed in to change notification settings - Fork 42
Separate code quality checks #8
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
Conversation
There is no need to run its checks on each environment.
It is not yet activated because there are way to many flake8 failures in this package.
bcd7771 to
75c375d
Compare
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.
Accept from the two little details, for which it would be good to have a reason, it looks good to me.
.travis.yml
Outdated
| - pip install tox coveralls coverage | ||
| script: | ||
| - tox -e py | ||
| - tox -e py,isort |
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.
Here we might also want a run of the flake8 testenv, or is there any specific reason not to do so?
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.
The reason is that this package contains tons of flake8 violations which I did not yet wanted to fix for this PR.
| @@ -1,13 +1,13 @@ | |||
| [tox] | |||
| envlist = coverage-clean,py{27,34,35,36,py},coverage-report | |||
| envlist = coverage-clean,py{27,34,35,36,py},coverage-report,isort | |||
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.
Flake8 is also not called as a standard testenv here
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.
dito
There is no need to run the code quality checks along with the unit tests for each environment.