-
Notifications
You must be signed in to change notification settings - Fork 182
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
Not Working After 3.8 Upgrade #2465
Comments
Open |
Oh wow, thank you @rchl. Running that caused me to see the details about python 3.8 in To anyone else who might arrive here, try running the command @rchl said, and adding v4 with:
|
The recommendation is to not override the default setting as it already includes those. (unless you of course want to also add some channels of your own but most people don't do that) |
Describe the bug
Hate making a bug report that is essentially "it isnt working" but that's where Im at. Everything was fine until a couple weeks ago or so (vague for me because Ive been ignoring that LSP-Copilot stopped working for a bit but wanted to fix that today).
Having read many issue threads here I know that there was a recent upgrade to Python 3.8. I tried reinstalling LSP and LSP-Copilot in order to debug, but those steps arent working and not a single LSP or Copilot command will show up in my sublime's command prompt at all (yes Ive restarted a bunch and followed the guides in both projects).
After isolating LSP (e.g.; I removed copilot for now), and checking Subllime's logs on startup, I see the following issues (I'll follow with the full logs later):
To Reproduce
Steps to reproduce the behavior:
LSP:
show up in the command prompt. Only the one to set its settings.Expected behavior
Expect to be able to run LSP commands and install additional LSP packages in a working manner.
Screenshots
N/A
Check https://lsp.sublimetext.io/troubleshooting/#self-help-instructions on how to provide additional logs.
Environment (please complete the following information):
VERSION
file in my installed version says2.0.0
.Additional context
N/A
The text was updated successfully, but these errors were encountered: