-
-
Notifications
You must be signed in to change notification settings - Fork 580
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
Unstable (non-idempotent) isort behavior. #1546
Unstable (non-idempotent) isort behavior. #1546
Comments
Isort itself is installed in the current active environment. I am using poetry to manage dependencies. If you clone my project this should be able to reproduce it:
|
I left my repository at the current broken state. I know that I can use |
Thank you for reporting! This issue has been resolved in a hotfix release (5.6.1) and your project has been added to isort's integration test suite. Any time non-idempotent behaviour is observed with isort it is of major concern for the project. I was able to pinpoint the cause of the issue to two things:
Both of these issues have been resolved. Thanks! ~Timothy |
Thank you for the quick turnaround and explanation! |
I am seeing something weird on isort 5.6.0 and didn't seem to find something similar in the issue. When running
isort tests src
against my project (https://github.com/rocketDuck/dobby) multiple times I get the following output:As you can see isort fixes the file multiple times (adding and removing a blank line between imports) without any changes by me. I literally ran those commands one after another.
Additional information:
Running with
--verbose
shows that isort sometimes considers dobby FIRST and sometimes THIRDPARTY:vs
As to why isort behaves differently on subsequent runs I have no idea.
The text was updated successfully, but these errors were encountered: