-
Notifications
You must be signed in to change notification settings - Fork 2
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
Code Style #6
Comments
After comparing Black with other tools, it became apparent that the results of yapf are often more readable than Black's and that Black wastes a lot of vertical space without paying back strong enough value. Also, while having projects consistent across the ecosystem is an interesting idea, Black fixes the "wrong problem", because readability is key, not consistency across projects. So if I have a choice, I'd welcome yapf (or something like it), but vote against Black myself. |
PS: Same project with… |
And here's the yapf config that's in use today: https://github.com/git-big-picture/git-big-picture/blob/master/.style.yapf |
I think this is highly subjective but I don't see any value in discussing it with the current contributor count. I don't have strong opinions about both tools. If you think yapf is okay with the config you shared, I can apply it. |
I was thinking of adding black as code formatter but wanted to ask before creating the PR. @hahey @hartwork does it sound fine?
The text was updated successfully, but these errors were encountered: