Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
python-lsp-server
Fork of the python-language-server project, maintained by the Spyder IDE team and the community
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I am finally starting to use lsp for python development. I am using pylsp as LS.
I am reading here but still... it seems all OK. It is weird that it was working with ALE with the current setup. Anyway, I noticed that every once in a while I get this error when I change buffer.
I am finally starting to use lsp for python development. I am using pylsp as LS.
I tried something else that was really slow, jedi worked just fine so I've stuck with that. Running vim-lsc as the client.
[KINDA SOLVED]: I found the issue. Apparently there is a conflict with this plugin of which I am the author :D The mentioned plugin change some env variables and the vim internal sys.path and so far it was working with other plugins that I tested so far but it does not seems to work with LSP. Perhaps it is due to that when you change virtual environment you also change the path of the executable and I initialize the LSP at VimEnter as it follows?