Not working on Arch Linux with pyenv

[superlou]

          It there anyone can set this up now? i try to install python-lsp-server on my system, in a virtualvenv, it just show not thing to me

I'm using Arch Linux and pyenv? Maybe that's the problem?

Originally posted by @ppvan in #13 (comment)

[superlou]

Are you starting lapce from within the virtual environment? If run pylsp --version in the virtual environment, what is the output?

[ppvan]

I'm install pylsp on my system and test it in lapce with simple main.py (No venv at this point)
Not thing show up, i tried pylsp --help and kinda sure that's it on my PATH and working
Then i try to reinstall every thing in venv, activate it from terminal and see what's going
I don't get the start lapce in venv part? How can i do that? If i start lapce from terminal, it just start and lapce show up (just like in the background, no output)

Finally, pylsp --version output pylsp v1.7.2

[ppvan]

This thing is strange to me, start lapce from terminal looks like this

[ppvan]

@superlou I'm getting this thing to work now, with a bit of manual labor

1. Open terminal, go to project directory and activate the python virtualenv
2. Start lapce from terminal, in venv shell
3. Autocomplete works now

But it doesn't seem to work in system pip, that's not matter because every one work in venv. But i'm really expect it to detect my venv or allow me to set Python interpreter.

[superlou]

@ppvan, right now, I think those steps are how I expect it to work if you have a non-system configuration in the venv. It does work on my Linux Mint and Windows 10 computers using the system python3 environment. The plugin doesn't have any intelligence to detect the presence of a venv, other than having Lapce started within the venv.

[ppvan]

Yeah, i think we need to modify lapce to have a chance to do it Vào 18:25, Th 2, 17 thg 4, 2023 superlou ***@***.***> đã viết:

…

@ppvan <https://github.com/ppvan>, right now, I think those steps are how I expect it to work if you have a non-system configuration in the venv. It does work on my Linux Mint and Windows 10 computers using the system python3 environment. The plugin doesn't have any intelligence to detect the presence of a venv, other than having Lapce started within the venv. — Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQT6DULFUN6CMAO4XDSYRVLXBUSCNANCNFSM6AAAAAAW6X46FA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Packman28334]

I can confirm it works on Arch Linux only when Lapce is started from the venv.

I also tested installing the package from pipx, which puts pylsp on PATH and allows the command to work outside of the venv, but the language server still does not start in Lapce. Of course, supporting the pipx version wouldn't solve the issue of Lapce not supporting different interpreters, and the modules exclusively in the venv wouldn't have intellisense, but it would at least be an interim solution to point people to until it's updated. Having intellisense for just stock modules is still better than no intellisense at all.

[superlou]

Are there other Lapce LSP plugins that work with venvs? Maybe we could get some inspiration from those.