Currently the plugin supports pyright out of box. Is there any plannings of support other python LSP such as https://github.com/python-lsp/python-lsp-server and https://github.com/pappasam/jedi-language-server.

README is using plugin name nvim-lua/completion.nvim.

It effectively prevents installing this plugin.

It shall read nvim-lua/completion-nvim

Python LSP server:

• pyright
• jedi
• pylsp
• python-lsp-server
• ruff-lsp

Hey,

Thanks for the work!

Would it be possible to make py_lsp read the venv property of pyproject.toml (thinking about conda envs).

After installing the plugin:

E5113: Error while calling lua chunk: ...m/site/pack/packer/start/py_lsp.nvim/lua/py_lsp/init.lua:1: module 'telescope.pickers' not found:
        no field package.preload['telescope.pickers']
        no file './telescope/pickers.lua'
        no file '/__w/neovim/neovim/.deps/usr/share/luajit-2.1.0-beta3/telescope/pickers.lua'
        no file '/usr/local/share/lua/5.1/telescope/pickers.lua'
        no file '/usr/local/share/lua/5.1/telescope/pickers/init.lua'
        no file '/__w/neovim/neovim/.deps/usr/share/lua/5.1/telescope/pickers.lua'
        no file '/__w/neovim/neovim/.deps/usr/share/lua/5.1/telescope/pickers/init.lua'
        no file './telescope/pickers.so'
        no file '/usr/local/lib/lua/5.1/telescope/pickers.so'
        no file '/__w/neovim/neovim/.deps/usr/lib/lua/5.1/telescope/pickers.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
        no file './telescope.so'
        no file '/usr/local/lib/lua/5.1/telescope.so'
        no file '/__w/neovim/neovim/.deps/usr/lib/lua/5.1/telescope.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
        [C]: in function 'require'
        ...m/site/pack/packer/start/py_lsp.nvim/lua/py_lsp/init.lua:1: in main chunk
        [C]: in function 'require'
        ...user/.config/nvim/lua/settings.lua:46: in main chunk
        [C]: in function 'require'
        /home/user/.config/nvim/init.lua:2: in main chunk

There is an undefined reference to M.stop_client() (a possible typo?) in the Telescope picker. I've submitted a PR #25 with the fix.

So I had poetry that was crashing and the :checkhealth showed:

So my issue generated that error that I fixed #37 with a fallback but could be interesting a check with a popup in case the poetry (in this case) generate error.

I am not sure how I can help debug this issue.

But I use lsp-zero and mason to install and configure lsp servers.

After adding py_lsp I see the following error when I open a python file with nvim.

Spawning language server with cmd: `pylsp` failed. The language server is either not installed, missing from PATH, or not executable.

The funny thing is that it does seem like the pyright lsp and the venv is activated.

Another curios thing is that the error message persists even after I remove py_lsp, which makes me wonder if py_lsp made a change somewhere that is not undone when you remove it.

Please let me know if I can run any debug steps on my side.

Due to deprecation use new lsp installer: https://github.com/williamboman/nvim-lsp-installer

Its annoying to wait for a pip install to finish.
Also maybe do a auto reload of lsp server after so, the changes in site-packages are seen by Pyright

With this code you can see

require'py_lsp'.setup({
    language_server = "pylsp",
    source_strategies = {"poetry", "default", "system"},
    capabilities = capabilities,
    on_attach = on_attach,
    pylsp_plugins = {
        pyls_mypy = {
            enabled = true
        },
        rope_autoimport = {
            enabled = true
        },
        rope_completion = {
            enabled = true
        },
        pyls_isort = {
            enabled = true
        },
        pycodestyle = {
            enabled = false,
        },
        flake8 = {
            enabled = true,
            executable = venv_bin_detection("flake8"),
        }
    }
})

That on setup pylsp_plugins and the others are empty, excluded source_strategies.

You can check the issue with:

  local ok, notify = pcall(require, "notify")
  for k, v in pairs(opts) do
  if type(v)=='table' then
      notify.notify(k .. table.concat(v, ','), "info", {
        title = " py_lsp.nvim",
        timeout = 300,
      })
  end

On setup function.
I saw this issue as the LSP is not applying the plugins, the data are there but they are not passed in the rest of the plugin.

I noticed this is already on your todos, but it would be a really nice feature to see. It seems like you could integrate it pretty easily by searching the envs path at the conda installation location (usually something like ~/conda). I was able to follow the example here to create my own little change Python interpreter code:

function change_python_interpreter(path)
    vim.lsp.stop_client(vim.lsp.get_active_clients())
    configs.pyright.settings.python.pythonPath = path
    require'lspconfig'.pyright.setup(configs.pyright)
    vim.cmd('e%')
end

function get_python_interpreters(a, l, p)
    local paths = {}
    local is_home_dir = function()
        return vim.fn.getcwd(0) == vim.fn.expand("$HOME")
    end
    local commands = {'fd --glob -tl python $HOME/mambaforge', 'which -a python', is_home_dir() and '' or 'find . -name python'}
    for _, cmd in ipairs(commands) do
        local _paths = vim.fn.systemlist(cmd)
        if _paths then
            for _, path in ipairs(_paths) do
                table.insert(paths, path)
            end
        end
    end
    table.sort(paths)
    local res = {}
    for i, path in ipairs(paths) do
        if path ~= paths[i+1] then table.insert(res, path) end
    end
    return res
end

vim.api.nvim_exec([[
command! -nargs=1 -complete=customlist,PythonInterpreterComplete PythonInterpreter lua change_python_interpreter(<q-args>)

function! PythonInterpreterComplete(A,L,P) abort
  return v:lua.get_python_interpreters()
endfunction
]], false)

This provides a PythonInterpreter vim command which offers completion options of all conda environments and works well for me. However, I like what you are doing with this plugin much better.

Not happy with just using raw tables with strategies and paths. Maybe use metaclasses venvs and be more descriptive and less hacky

https://github.com/kabouzeid/nvim-lspinstall is a convenient plugin to install LSP servers. They end up in a separate directory outside of $PATH (~/.local/share/nvim/lspinstall/python/./node_modules/.bin/pyright-langserver in my case), but https://github.com/kabouzeid/nvim-lspinstall/blob/54b439241e83e0a9ce8f6bcdf3b2c560a2328792/lua/lspinstall.lua#L94 corrects the default cmd for lspconfig to point to that location. However py_lsp doesn't pick up on it for some reason, perhaps overriding cmd or cmd_cwd in default_config?

This is with py_lsp installed and used to set up Pyright:

And this is with py_lsp disabled: (note cmd)

Instead of using own popup functionality use telescope

Hi, thanks for you plugin. I just installed it and noticed that it's useful for me.
But I have a question about usage workflow.
When I open the project with venv folder inside, nvim not using this venv, until I run this command:
:PyLspActivateVenv

I thought that It will be simpler if nvim will look for some directories (venv, .venv, py) and if one of them exists (and contains venv), it will be activated automatically.

Isn't this the desired plugin behavior for everyone? Or did I miss something?

So when running this command I get this error

Doing some research (and editing my stratagies.lua the function table.unpack isn't available in older versions of lua info - any way I was able to fix it by removing the table.

Is this something you want to fix ? or should we recommend users update there Lua to 5.2 ?

https://github.com/nvim-lua/nvim-package-specification

Include notify to docs and more stable and expressive....Maybe a nice image

Make docu in general more clean.

• Update for PyRun #28
• Find venvs logic

Hi, thanks for the plugin! I'm currently deciding on my Python workflow and this'll probably make the cut. :) I have two improvements to suggest:

1. It seems unnecessary to demand the completion plugin. It only appears in the default on_attach setting and can be safely removed.
2. It'd be good to also expose a capabilities field when passing options to require'lspconfig'.setup as that's where you turn on snippet support.

There's an option to automatically source from PyLspFindVenvs results? I mean, I always have a .venv on my project root so there's any way to pass the PyLspFindVenvs results automatically activation?

they are replaced accordingly with vim.health.start() and ok().

For some nicer debuggin and traceablity

When reloading the lsp(s), the Pyright server is not getting started again