-
Notifications
You must be signed in to change notification settings - Fork 564
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
style: fix isort config #1817
style: fix isort config #1817
Conversation
basically the same as #1798 - again would like to know what people think, I think it is useful but would be fine to leave it also if it bothers anyone too much. |
Okay actually isort is doing nothing, so this PR will be basically just adding isort with working config. |
a1615ac
to
b723519
Compare
As with #1798 - if everyone is in agreement I will rebase, comment "pre-commit.ci autofix" and merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to have it actually touch the Python files, given that's what it's for!
@gjhiggins good to have your feedback here also. Don't want to make anyones life harder, so if we should look at ways of making these things less onerous on developers we should look at it. |
`isort` was misconfigured to only touch `*.{pyw,pyi}` files. This patch fixes isort config so that it actually does sort imports. It also removes the attempt to ignore the test directory.
b723519
to
520bdda
Compare
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
Summary of changes
isort
was misconfigured to only touch*.{pyw,pyi}
files.This patch fixes isort config so that it actually does sort imports.
It also removes the attempt to ignore the test directory.
Checklist
the same change.
so maintainers can fix minor issues and keep your PR up to date.