-
Notifications
You must be signed in to change notification settings - Fork 124
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
Formatting with black #204
Conversation
tests/system/test_gbq.py
Outdated
assert len(df.drop_duplicates()) == 10 | ||
|
||
def test_standard_sql(self, project_id): | ||
standard_sql = "SELECT DISTINCT id FROM " \ | ||
"`publicdata.samples.wikipedia` LIMIT 10" | ||
standard_sql = "SELECT DISTINCT id FROM " "`publicdata.samples.wikipedia` LIMIT 10" |
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.
E501 line too long (91 > 79 characters)
fixups and config
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.
I'd be happy to update to this workflow and am okay with the one-time cost of a few (or a lot) of merge conflicts.
We could probably change the "lint" session in nox.py to run changes through black and complain if there's any diff afterward. That pattern is pretty common in Go projects I've worked on.
Sounds good to me. Thanks for adding this, @max-sixty ! |
@tswast please could you take a final look before I merge? I changed Stickler to use black rather than running in Travis on nox |
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.
Thanks!
As an example of how the repo would look using https://github.com/ambv/black
I find this great for repos I'm starting. I'm not sure it's worth the tradeoff of merge conflicts for existing projects, though.