forked from emissary-ingress/emissary
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request emissary-ingress#4313 from emissary-ingress/lukesh…
…u/black Add the `black` Python code formatter It's silly how many code review comments are about formatting of Python code. Mechanical things like that are the job of computers, not human reviewers. For many years, there were many competing Python code formatters. However, in the last couple of years, the Python community has come to a realization that the Go community realized from the get-go: Agreement on the formatter is more important than the formatting itself. That even if the formatting isn't your favorite, that not having to have discussions about formatting is even better. So the Python community has standardized on the `black` formatter. So adopt `black` the way we've adopted `gofmt`! - The first 2 commits are addressing things to get them ready for black - The 3rd commit is adding black in to our tooling, but not yet committing the results of running black - The final commit is just running `make format/black` (running just `make format` would do this and a few other things too) That last commit, while being machine-generated, is probably still worthy of decent scrutiny, to make sure it didn't move around a comment to where it's not near the code it's describing, or something funny like that. I considered turning parts of black off, and only re-formatting things incrementally over time, so as to avoid merge-conflicts with current in-flight Python work. While tempting, there's still no good time to turn each thing on, so I figure it's better to just bite the bullet and get it over with rather than drawing it out over months. Signed-off-by: Luke Shumaker <[email protected]>
- Loading branch information
Showing
178 changed files
with
15,078 additions
and
9,366 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
[tool.black] | ||
line-length = 100 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.