-
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
Run Black #9512
Comments
The thing that's in review is probably this: #1049 But right now that's nothing but a mess of conflicts and can't be merged, more or less as one would expect. We really need a tool that we can run against arbitrary other branches so that this won't be so disruptive to everyone working on changes in progress. Once we have that with some good documentation (does Black already have such a thing?) we should probably have the actual run-Black-on-everything PR skip the normal process. |
Put the PR back up for review. Since we dropped 2.7 compat and we're starting to sprinkle in type annotations, I think that black would be extra useful to help reduce the formatting legwork. I also believe that if you merge in this merge commit, blackify your PR, then merge trunk, git should know what to do. If we squash merge PRs, then we'll also get a nice history for those PRs. |
|
Approved here: #1134 (review) Thanks so much for this! It will make Twisted development much more pleasant. |
See: #9498
Searchable metadata
The text was updated successfully, but these errors were encountered: