This repository was archived by the owner on Jun 12, 2025. It is now read-only.
Add black formatting #17
Merged
Conversation
This file contains hidden or 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
9dc950b to
aff175f
Compare
0cd54dd to
9cc946d
Compare
9cc946d to
e964817
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Add a new linting module to CI. Fix outstanding mypy errors. We currently only check the main library and ignore the examples folder, since examples let people go off-road a bit more.
The diff ended up being pretty minor so existing PRs should be able to merge in automatically, with perhaps a few manually resolved conflicts. Alternatively these PRs can also rebase on
mainand run formatting to avoid unnecessary merge conflicts:scikit-learn/scikit-learn#20301
https://stackoverflow.com/questions/65304887/what-is-the-best-way-to-resolve-git-conflicts-after-reformatting-entire-python-c