[Question] Virtual environments?

[TitaniumHocker]

Hello!

First of all thank you guys for supporting this fork.

I'm using neovim as my main code editor and right now I'm trying to migrate from coc.nvim to native neovim LSP client implementation(which is still in development btw).

So, I don't figured out how to configure this language server to use executables from virtual environment instead of global scope of my system. For example from python venv or pipenv. In coc It was enough just to specify configuration parameter "python.pythonPath" with the full path to the python executable file in the virtual environment and everything works fine.

Tech information above
System: Manjaro GNU/Linux
LSP Client: neovim v0.5.0-dev

[yeraydiazdiaz]

I wondered about this too, maybe I'm missing something but using Sublime Text I specify the pylsp executable which starts the server in its own virtual environment. Plugins, built-in and external, import the libraries and from that virtual environment and returns responses, however, the versions of these libraries may be different than those of the project I am working on (with the exception of pyls-flake8 which invokes a subprocess).

To be fair this is generally not a problem for most plugins since they don't change that much between versions anyway, but in other editors like PyCharm or VSCode you'll be prompted to install the missing library in your virtual environment.

Am I correct in that interpretation? Is this a problem in the design of pylsp or something that could be solved at the plugin level?

[yaegassy]

I used "coc.nvim" to create coc-pylsp for "verification". https://github.com/yaegassy/coc-pylsp

It is only for verification, so it is not published on npm.

Why not just detect the pylsp command and invoke it without determining whether it is a global or virtual environment?

If you want to use pylsp and more tools, any version at the project level, I guess the approach would be to install pylsp in a virtual environment.

[TitaniumHocker]

I can run nvim from venv shell and the language server will work file, but only if language server and pynvim is installed in this venv. Installing this packets for every project venv seems wasteful to me.

[yaegassy]

I have pynvim installed on a system global basis. However, I think it works fine in "venv". I don't think running a language server has anything to do with pynvim, but if I'm wrong, I'm sorry.

[TitaniumHocker]

I have an error if pynvim is not installed in venv:

No "python3" provider found. Run ":checkhealth provider"

May be it's only in my configuration.

[yaegassy]

This is an excerpt in my environment. No problem.

## Python 3 provider (optional)
  - INFO: Using: g:python3_host_prog = "/usr/local/bin/python3"
  - INFO: Executable: /usr/local/bin/python3
  - INFO: Python version: 3.9.5
  - INFO: pynvim version: 0.4.3
  - OK: Latest pynvim is installed.

## Python virtualenv
  - INFO: $VIRTUAL_ENV is set to: /private/tmp/venvcheck/venv
  - INFO: Python version: 3.9.5
  - OK: $VIRTUAL_ENV provides :!python.

The pynvim thing has nothing to do with pylsp, so you can ask about it on Neovim's "gitter" or "issue".

[TitaniumHocker]

I worked some days with using separate lsp server to each venv, works fine. So, I'll close the issue. Thanks for help.

[weeman1337]

Hi @TitaniumHocker so you are installing python-lsp-server in every project? To me that looks like a huge overhead. Did anybody find out how to install python-lsp-server globally or in a separate virtualenv and point it to the project currently working on?

[meshy]

Neovim 0.5 is out now, so this is no longer just for pre-release. Installing pylsp in the venv feels like a hack, and is a frustrating
step to have to repeat after rebuilding venvs.

Thankfully I'm not using a stricter python package manager that would object to the extra package.

I am still looking for a solution to this that makes it work more like my previous setup in neovim.

[ccordoba12]

We provide the option pylsp.plugins.jedi.environment to configure your preferred environment, so you need to make use of it (see our configuration description file).

Note: This is something that needs to be solved client-side, so please stop posting comments here and open an issue in Neovim or your other editors or IDEs to add support for that.

[meshy]

Apologies for the noise. Thanks for the pointer.

[apapsch]

My global pylsp script:

#!/bin/sh
pipenv scripts > /dev/null 2>&1 || {
    echo "run pylsp inside directory with Pipfile"
    exit 1
}
exec pipenv run pylsp "$@"

Please mind the hack. 🚂