-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update plugin to use python-lsp-server instead of python-language-server #42
Comments
Hey @andfoy, thanks for opening an issue here! |
I'm facing this issue where This extension depends on You can see my changes in the PR https://github.com/QuantStack/pyls-memestra/pull/43/files and here's a screenshot: The As you can see other plugins that are dependent on Any leads on what I might be doing wrong will be of great help! |
I think you forgot to use |
True! |
Closing this issue. A new version will come out as soon as a new version of jupyter-lsp comes out too :) |
Hi,
Given that Palantir removed all the community maintenance for both python-language-server (pyls) and python-jsonrpc-server (pyls_jsonrpc), we decided to create a separate organization that now maintains a community-based fork for the aforementioned packages, which can be found at: https://github.com/python-lsp/python-lsp-server and https://github.com/python-lsp/python-lsp-jsonrpc.
Our recommendation is to migrate this plugin to be compatible with the community server instead of the Palantir one. In order to do so, here is a migration guide that should help:
python-language-server
bypython-lsp-server
on its requirements.pyls
namespace is nowpylsp
, which means that allpyls
imports should be replaced bypylsp
.pyls_*
hookspecs are nowpylsp_*
hookspecs.pyls_
prefix on its namespace in order to prevent further administration and release issues that may arise from renaming it.Feel free to ask any question about the migration process or about the new community organization for the server.
The text was updated successfully, but these errors were encountered: