-
Notifications
You must be signed in to change notification settings - Fork 36
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
Is there any plan to migrate pygls to v2.0? #546
Comments
I see the https://pygls.readthedocs.io/en/latest/howto/migrate-to-v2.html#renamed-languageserver-methods |
After some trying, i give it up, maybe that's beyond my ability. 🤣 |
@Snoopy1866 |
@karthiknadig ended up stumbling across this... don't you think it's strange that Esbonio is breaking this extension? Since we both ship our own Python envs, and they are installed into separate directories, they should be separate right? Just wondering if I'm doing something wrong I guess! 😅 |
This can happen when, the mode is set to prioritize packages installed in the environment. Here, lsp server implementation is pulling I am planning on changing this in a way where will pre-load the packages that are needed for the server. |
I'm using
black formatter
andesbonio
simutaniously. I found the pre-release of esbonio has updated the pygls to 2.0.0a1, which is incompatible withblack formatter
.pygls v2.0.0a1 cause Black Formatter server crashed 5 times in the last 3 minutes, same as #189
Below is the output:
Full output
I wonder if there is a plan of migrating pygls to v2.0?
The text was updated successfully, but these errors were encountered: