-
Notifications
You must be signed in to change notification settings - Fork 2
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
revise import headers #18
Comments
I've wanted to clean this up for a long time, but I'm not seeing those warnings. (I'm not sure if my VS Code settings have them disabled.) |
Here are the warnings from
|
...and here is the same, only this time without disabling
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently pylint is giving
(unused-import)
style warnings for many files. This isn't critical during early development but I don't see a reason why we can't drop all unused imports and then add them back when/if we actually need them.Also, many files import almost the same packages, but in slightly different orders with subtle changes in what is added and dropped.
Although pylint
(wrong-import-order)
is quite opinionated -- I believe it requires built in, then third party, then module imports, with froms second in each group -- it might be useful to conform to it, as this would give consistency over a large number of big import headers.The text was updated successfully, but these errors were encountered: