Open jaapz opened 4 years ago
It appears what's going on is that isort
doesn't do the same 'search for settings' when consuming input via stdin vs. when it is passed path to a file. It doesn't use the current working directory to search for settings files when consuming from stdiin.
However, as a workaround, setting
let g:ale_python_isort_options = '--settings-path .'
will get isort to find the right settings file (including a pyproject.toml, that's what I'm using).
This appears to be fixed now. I've tested this using isort 5.2.2
on vim8 with ale 2.6.0
and on neovim using the latest on master
for ale, and isort now finds my settings in pyproject.toml
as expected. So no more need for the workaround I posted above.
@w0rp I think this is safe to close
Could you @jaapz please confirm what @mfogel wrote above, and close this stale issue if it is resolved?
Information
VIM version
Operating System: arch linux
What went wrong
When enabling the
isort
fixer, it does not respect settings defined inpyproject.toml
in the project directory. I think this is the same problem theblack
fixer had which was fixed like this: https://github.com/dense-analysis/ale/pull/2262Reproducing the bug
Put some isort config in
pyproject.toml
, for example:Watch
isort
not care about your config:ALEInfo