Blacken repo #218
Merged
Blacken repo #218
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR uses
blackandisortto auto-format the repo. These tools are developed by PSF and PyCQA and used by many projects to enforce a common PEP-8 compliant standard. Unlikeflake8, these tools are auto-formatters, so if someone submits a PR that doesn't pass these tests, they simply need to runblack .orisort .in the repo and it will solve all of their issues. This was incredibly useful when working on #215 since the type hints I added increased the line length of most function signatures above the 88 character limit. Downside is thatgit blameis much less useful now since this PR affects most files. But the same will be true with #215 since it edits every function signature.