jupyterlab-lsp: Several inconsistencies found, trying to configure pylsp
This project’s main README describes installing an example server like so, using the Advanced Settings Editor:
{
"language_servers": {
"pyls": {
"serverSettings": {
"pyls.plugins.pydocstyle.enabled": true,
"pyls.plugins.pyflakes.enabled": false,
"pyls.plugins.flake8.enabled": true
}
},
"r-languageserver": {
"serverSettings": {
"r.lsp.debug": false,
"r.lsp.diagnostics": false
}
}
}
}
But when trying to use the settings for Language Servers, since recently called “Language Servers (Experimental)”, it seems one first needs to create a new language server with the right server name and manually activate it with a switch:
and then opening the JSON Settings Editor, some of the JSON keywords seem to not match above given instructions:
i.e.:
language_servers
is nowlanguageServers
- and
pyls(p).serverSettings
is nowpyls(p).configuration
(indicating the recommended replacement of pyls with pylsp).
Note, that this is just an observation of inconsistencies, while I tried to find out how to get a python lsp server running, which I haven’t been able to do so far. Something has changed as I was able to do to so before, even wrote a medium post about it…
Another observation: Anytime I added a property using the GUI, the terminal log said:
2024-02-06 13:18:26,728 CET - WARNING - pylsp_jsonrpc.endpoint - Ignoring notification for unknown method $/setTrace
About this issue
- Original URL
- State: open
- Created 5 months ago
- Comments: 16 (16 by maintainers)
Thank you, this is a bug. It should be there even if validation fails.
Personally I am not happy that upstream includes
Language Servers (Experimental)
but no LSP features (which are in this extension) - if it has no features, I would prefer it to not show that settings page at all, but was told that I can just replace it downstream here so here we are. Also there is so much I can do convincing other to embrace LSP features upstream. It really comes down to users voice (and funding).