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

Use pycodestyle for lint checks. #2642

Merged
merged 8 commits into from
Jan 3, 2019

Conversation

shoyer
Copy link
Member

@shoyer shoyer commented Jan 2, 2019

flake8 includes a few more useful checks, but it's annoying to only see it's
output in Travis-CI results.

This keeps Travis-CI and pep8speaks in sync.

flake8 includes a few more useful checks, but it's annoying to only see it's
output in Travis-CI results.

This keeps Travis-CI and pep8speaks in sync.
@dcherian
Copy link
Contributor

dcherian commented Jan 2, 2019

Looks like these need to be fixed:

xarray/tests/test_backends.py:2466:38: E741 ambiguous variable name 'l'
xarray/tests/test_backends.py:2466:58: E741 ambiguous variable name 'l'
xarray/tests/test_dataarray.py:445:9: E741 ambiguous variable name 'I'
xarray/tests/test_indexing.py:27:9: E741 ambiguous variable name 'I'
xarray/tests/test_indexing.py:137:9: E741 ambiguous variable name 'I'
xarray/tests/test_indexing.py:157:9: E741 ambiguous variable name 'I'
xarray/tests/test_indexing.py:214:9: E741 ambiguous variable name 'I'
xarray/tests/test_indexing.py:526:5: E741 ambiguous variable name 'I'
xarray/core/common.py:809:80: E501 line too long (80 > 79 characters)
xarray/core/dataset.py:1080:80: E501 line too long (81 > 79 characters)
xarray/core/dataset.py:2174:80: E501 line too long (80 > 79 characters)
xarray/core/dataset.py:2259:80: E501 line too long (80 > 79 characters)
xarray/core/pycompat.py:135:80: E501 line too long (81 > 79 characters)
xarray/core/pycompat.py:146:80: E501 line too long (81 > 79 characters)

@shoyer
Copy link
Member Author

shoyer commented Jan 2, 2019

@pep8speaks fix all

@pep8speaks
Copy link

pep8speaks commented Jan 3, 2019

Hello @shoyer! Thanks for updating the PR.

Cheers ! There are no PEP8 issues in this Pull Request. 🍻

Comment last updated on January 03, 2019 at 17:23 Hours UTC

@shoyer
Copy link
Member Author

shoyer commented Jan 3, 2019

I found a related issue on the pep8speaks tracker, opened by our own @fmaussion: pep8speaks-org/pep8speaks#96

@shoyer
Copy link
Member Author

shoyer commented Jan 3, 2019

Lint is passing on Travis-CI now, so I'm going to merge this.

@shoyer shoyer merged commit 28123bb into pydata:master Jan 3, 2019
dcherian pushed a commit to yohai/xarray that referenced this pull request Jan 24, 2019
* master:
  Remove broken Travis-CI builds (pydata#2661)
  Type checking with mypy (pydata#2655)
  Added Coarsen (pydata#2612)
  Improve test for GH 2649 (pydata#2654)
  revise top-level package description (pydata#2430)
  Convert ref_date to UTC in encode_cf_datetime (pydata#2651)
  Change an `==` to an `is`. Fix tests so that this won't happen again. (pydata#2648)
  ENH: switch Dataset and DataArray to use explicit indexes (pydata#2639)
  Use pycodestyle for lint checks. (pydata#2642)
  Switch whats-new for 0.11.2 -> 0.11.3
  DOC: document v0.11.2 release
  Use built-in interp for interpolation with resample (pydata#2640)
  BUG: pytest-runner no required for setup.py (pydata#2643)
@fmaussion
Copy link
Member

@shoyer pep8speaks now support #noqa : pep8speaks-org/pep8speaks#96 (comment)

I wonder if it's still relevant for us since your change though.

@shoyer shoyer deleted the travis-pycodestyle-checks branch March 14, 2019 06:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants