Incorrect identification of first and third party modules
zsofiak96 opened this issue · comments
Zsófia commented
I came across the issue that isort
identifies the first party modules as third party, and reorders the way my imports are sorted.
In my CI/CD I have a test job set up where the module detection seems to work, and since I have incorrectly sorted my imports locally, when I push changes, my test pipeline fails.
I have the same Python and isort
versions pinned in both environments.
The issue occurs irregularly.