-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
Move flake8-related packages deps to reqs-dev.txt #5460
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5460 +/- ##
=======================================
Coverage 59.11% 59.11%
=======================================
Files 372 372
Lines 23751 23751
Branches 2758 2758
=======================================
Hits 14041 14041
Misses 9695 9695
Partials 15 15 Continue to review full report at Codecov.
|
requirements-dev.txt
Outdated
redis==2.10.6 | ||
statsd==3.2.2 | ||
tox==3.1.2 | ||
console_log==0.2.10 | ||
pylint==1.9.2 | ||
flake8==3.5.0 |
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.
Nit. Can we try to keep these packages in alphabetical order.
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.
LGTM. Could you address the comment about the alphabetical order?
My VIM which is integrated with flake8 wouldn't match the output from travis and would often miss things related to the flake8 plugins installed using Tox. By moving this to requirements-dev.txt, we can expect developers would have the proper configuration locally and get matching results with Travis when running flake8 or in their IDEs if its integrated with flake8..
* Move flake8-related packages deps to reqs-dev.txt My VIM which is integrated with flake8 wouldn't match the output from travis and would often miss things related to the flake8 plugins installed using Tox. By moving this to requirements-dev.txt, we can expect developers would have the proper configuration locally and get matching results with Travis when running flake8 or in their IDEs if its integrated with flake8.. * merging migratinos * sorting packages * Specify folder for flake8 processing * pin pycodestyle==2.3.1 * merge db migrations
* Move flake8-related packages deps to reqs-dev.txt My VIM which is integrated with flake8 wouldn't match the output from travis and would often miss things related to the flake8 plugins installed using Tox. By moving this to requirements-dev.txt, we can expect developers would have the proper configuration locally and get matching results with Travis when running flake8 or in their IDEs if its integrated with flake8.. * merging migratinos * sorting packages * Specify folder for flake8 processing * pin pycodestyle==2.3.1 * merge db migrations (cherry picked from commit fee5023)
* Move flake8-related packages deps to reqs-dev.txt My VIM which is integrated with flake8 wouldn't match the output from travis and would often miss things related to the flake8 plugins installed using Tox. By moving this to requirements-dev.txt, we can expect developers would have the proper configuration locally and get matching results with Travis when running flake8 or in their IDEs if its integrated with flake8.. * merging migratinos * sorting packages * Specify folder for flake8 processing * pin pycodestyle==2.3.1 * merge db migrations
My
vim
which is integrated with flake8 wouldn't match the output fromtravis and would often miss things related to the flake8 plugins
installed using Tox.
By moving this to requirements-dev.txt, we can expect developers would
have the proper configuration locally and get matching results with
Travis when running flake8 or in their IDEs if its integrated with
flake8.