When a python file A(main.py in the screenshot) has no mypy error but file B(foo_module.py) does, the error in the latter is shown in the buffer of file A.
I am not sure this is an intended behaviour, but I think showing them in import statement line makes more sense if users want mypy errors of other files to be shown.
Environment
macOS 10.15.6
neoVim v0.4.3
coc.nvim version 0.0.78-56999634f4
coc-python 1.2.12
Steps to reproduce
I included coc-settings.json and poetry config files to setup the minimum environment to reproduce this behaviour.
When a python file A(
main.py
in the screenshot) has no mypy error but file B(foo_module.py
) does, the error in the latter is shown in the buffer of file A.I am not sure this is an intended behaviour, but I think showing them in import statement line makes more sense if users want mypy errors of other files to be shown.
Environment
macOS 10.15.6 neoVim v0.4.3 coc.nvim version 0.0.78-56999634f4 coc-python 1.2.12
Steps to reproduce
I included coc-settings.json and poetry config files to setup the minimum environment to reproduce this behaviour.
https://github.com/TatchNicolas/coc-mypy-wrong-buffer
git clone https://github.com/TatchNicolas/coc-mypy-wrong-buffer.git && cd coc-mypy-wrong-buffer
poetry install
Open
main.py
which importsbar_module.py
which importsfoo_module.py
which has a type hint error at line 4You'll see the type hint error in
main.py
on which line 4 is actually an empty line.