You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The plugin should replace python-language-server by python-lsp-server on its requirements.
The pyls namespace is now pylsp, which means that all pyls imports should be replaced by pylsp.
The pyls_* hookspecs are now pylsp_* hookspecs.
The plugin can preserve the 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:
@rupert Is there a chance you could review #37, merge it and release a python-lsp-server-compatible version to PyPI? That would be great for all users of the plugin.
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: