-
-
Notifications
You must be signed in to change notification settings - Fork 389
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
isort as part of the CI pipeline #804
Conversation
isort needs to be set to use a black compatible configuration: https://github.com/python/black#how-black-wraps-lines (described at the bottom of this section)
From command line, or:
in .isort.cfg |
Ok, gave that I shot, but still coming back with a set of reformats. Running
|
Also is globbing stable? Or am I supposed to direct There's a series of 3x commits in this PR where I was getting different results simply by running (Also the commit msg for |
I believe, the best way to do this in isort is I made a small commit to develop, that removes the other cause of issues - I believe, which is the old usage of .editorconfig to specify some isort settings (b2f82aa) |
Ok, I think we can merge this branch actually (even though that wasn't the original intent). Or if you want to get rid of the comment noise, happy to open another PR on a branch with a better name. |
No need, I'm fine keeping the comment history. This is awesome! Thank you! |
Opening a dummy PR to get a little feedback re
isort
. The last 3x commits have been little experiment runs againstisort
andblack
.When I run
isort -c hug/*py
on the latest commit I get the following.It seems
black
is also in a bit of a tug-of-war withisort
, but I haven't looked closely enough to really understand it (yet).