-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Is pep8speaks working well? #2627
Comments
@max-sixty Personally, I feel it is not the best solution for the smooth development. If you have an alternative in your mind and could set it up, it'll be super nice. |
I think I need to be more careful to check the first comment for PEP8 issues before merging -- I've been relying on the green checkmarks. |
OK great - I've PRed changes to get back to zero It would be good if pep8speaks added a check too, but looks like it's not available. We could either:
|
@max-sixty Is strict pep8 compliance supposed to be mandatory in xarray? Sometimes it makes more sense to violate PEP8 to improve readability. My PR #2553 has some examples - e.g. here where I deliberately used a longer line rather than two lines so that it was clearer that I was testing what happens when you concatenate a square of 4 datasets. On the other hand there are also some violations of pep8 in the PR which are just oversights, and did get lost in the (lengthy) discussion. Is strict pep8 compliance already supposed to be mandatory in xarray? Should any intentional pep8 violations be flagged using |
We do aim for strict PEP8 compliance, but this is hard to enforce without the automated checks. Cases where it's violated intentionally can be marked with a comment. |
My vote is:
...so by-and-large do whatever you think is best, but make the checks pass with a comment where the code violates a standard |
Down a level: |
Let's add a build check of some sort for flake8, maybe to use alongside pep8speaks? |
Closed via #2632 |
I returned to do some work on xarray, and looks like there are lots of linting errors. Maybe we shouldn't worry ourselves with this; though let's make a deliberate decision
Is pep8speaks working well? One example is this PR: #2553, where it looks like pep8speaks initially complained, but doesn't have a test so was potentially lost in the discussion.
Any thoughts? I'm happy to help see if there are alternatives / pep8speaks can be added as a test / add a test in travis / fix these.
FWIW I've used
black
successfully in pandas-gbq and internally, but I think it's maybe too much change for a large project like xarrayThe text was updated successfully, but these errors were encountered: