-
Notifications
You must be signed in to change notification settings - Fork 40
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
Sort imports with Isort. #102
Conversation
Hi @TheQuinbox I tried isort last week and after running it on the source code bookworm failed to run. We've some problems with circular imports, unless we fix those, the tool will, actually, effect the functionality. I'll be keeping an eye on this PR. Best |
@mush42, I don't actually see how that's possible. AFAIK, Isort just moves code around (puts line breaks, indents extra long lines, etc). None of that should cause circular imports. I would test, but I'm currently unable to run Bookworm from source for... some reason. What files were causing the problem? |
Hello. |
@pauliyobo, if you could make it run, resolve the merge conflicts and merge it, that would be amazing! :). If not, I can close this, no issue there. |
@pauliyobo Is it safe to re-run isort on the code base without reservations? |
@mush42 It should be yes. |
No. I have no problems with adding pre-commit. |
I do. I'll add this tomorrow. |
Link to issue number:
None
Summary of the issue:
In Pep-8, it's convention to sort imports a certain way. There's a tool (Isort) that does this for us.
Description of how this pull request fixes the issue:
Added Isort to requirements-dev, and ran it on the entire codebase.
Testing performed:
None necessary (Isort doesn't change functionality), similar to Black.
Known issues with pull request:
None