pyls-mypy should use the :rootUri parameter to find the configuration file about pyls-mypy HOT 4 CLOSED

Thanks for reporting, great to hear this plugin working for Emacs users!

Although workspace is passed into pyls-mypy (exposing a root_path member), I am a bit unsure how it should improve your situation.

We use mypy as a library, so there is no mypy process to set a working directory on.

try to find the configuration file and pass it as an argument to mypy.

This is probably doable, but reading python/mypy#3377 I get the impression mypy expects to be run from the project root.

Taking mypy_ini_path as a config option from lsp-mode through pyls feels safer in that case, at least the user will be aware of the problem when they have to manually specify the config file.

Is there some design limitation preventing lsp-mode from changing to rootPath itself before starting pyls?

from pyls-mypy.

By using rootUri I meant doing a os.chdir before calling mypy, but that doesn't feel right. The configurable path seems like a better option. Yet another solution could be calling mypy in a different process.

Anyway, it feels strange fixing the problem here the way the plugin is implemented, that's why I reported the issue in lsp-mode in the first place. I don't know if this can be fixed in lsp-mode or not.

from pyls-mypy.

I don't have any time to work on this. But feel free to open a PR with a workaround!

from pyls-mypy.

@nilehmann

lsp-mode for emacs runs pyls in the directory of the first file visited in a project

This can be fixed by

  (lsp-define-stdio-client lsp-python "python"
                           #'projectile-project-root
                           '("pyls"))

  (add-hook 'python-mode-hook
            (lambda ()
	      (let ((root (projectile-project-root)))
		(if root
		    (progn
		      (cd root)
		      (lsp-python-enable))))))

from pyls-mypy.