You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you use the --filename option while streaming Python code to stdin for formatting, isort ignores configuration in the path for that filename.
Given a directory foo with .isort.cfg in that directory, I would expect that cat <somefile> | isort --resolve-all-configs --filename 'foo/bar.py' would use foo/.isort.cfg. Is that an incorrect expectation?
If I instead first use cd foo and then pipe Python source code through isort, the .isort.cfg configuration is correctly picked up.
The text was updated successfully, but these errors were encountered:
When you use the
--filename
option while streaming Python code to stdin for formatting, isort ignores configuration in the path for that filename.Given a directory
foo
with.isort.cfg
in that directory, I would expect thatcat <somefile> | isort --resolve-all-configs --filename 'foo/bar.py'
would usefoo/.isort.cfg
. Is that an incorrect expectation?If I instead first use
cd foo
and then pipe Python source code throughisort
, the.isort.cfg
configuration is correctly picked up.The text was updated successfully, but these errors were encountered: