Ruff now embeds an almost-fully-compatible formatter implementation of Black's 2023 stable style.
Now we can unify Black, Flake8, and isort into Ruff while ensuring the same linting rules.
This PR also fixes the mismatch of the mypy version in .pre-commit-config.yaml and requirements-dev.txt, updating it to the latest version 1.7.1.
Are there changes in behavior for the user?
No.
Checklist
[x] I think the code is well written
[ ] Unit tests for the changes exist
[ ] Documentation reflects the changes
[x] Add a new news fragment into the CHANGES folder
name it <issue_id>.<type> (e.g. 588.bugfix)
if you don't have an issue_id change it to the pr id after creating the PR
ensure type is one of the following:
.feature: Signifying a new feature.
.bugfix: Signifying a bug fix.
.doc: Signifying a documentation improvement.
.removal: Signifying a deprecation or removal of public API.
.misc: A ticket has been closed, but it is not of interest to users.
Make sure to use full sentences with correct case and punctuation, for example: Fix issue with non-ascii contents in doctest text files.
What do these changes do?
Ruff now embeds an almost-fully-compatible formatter implementation of Black's 2023 stable style. Now we can unify Black, Flake8, and isort into Ruff while ensuring the same linting rules.
This PR also fixes the mismatch of the mypy version in
.pre-commit-config.yamlandrequirements-dev.txt, updating it to the latest version 1.7.1.Are there changes in behavior for the user?
No.
Checklist
CHANGESfolder<issue_id>.<type>(e.g.588.bugfix)issue_idchange it to the pr id after creating the PR.feature: Signifying a new feature..bugfix: Signifying a bug fix..doc: Signifying a documentation improvement..removal: Signifying a deprecation or removal of public API..misc: A ticket has been closed, but it is not of interest to users.Fix issue with non-ascii contents in doctest text files.