Jack Cherng

Have you found a working old version yet?

> I don’t know how to roll back. After setting it up according to your method, it didn’t roll back to the previous version. It prevents package control from managing...

> I don’t know how to roll back. 1. Download the version you want. E.g., https://github.com/sublimelsp/LSP-pyright/archive/refs/tags/1.3.2.zip 2. Decompress and put it like ``` Packages └── LSP-pyright ├── commands.py ├── dependencies.json...

Just to confirm. `LSP-pyright` `1.3.0` and LSP `LSP-basedpyright` `1.1.0` both work for you and their next version failed, right?

Could you try this: https://github.com/sublimelsp/LSP-pyright/archive/refs/heads/fix/import-not-found.zip I doubt it may be fixed by https://github.com/sublimelsp/LSP-pyright/commit/273a22c3c97ef7eb87c15e9e95a061b5d084c8e6. This is the only behavior change that I notice between v1.3.0 and v1.3.1: https://github.com/sublimelsp/LSP-pyright/compare/1.3.0...1.3.1

Unfortunately, I still can't spot other behavior different between [1.3.0...1.3.1](https://github.com/sublimelsp/LSP-pyright/compare/1.3.0...1.3.1).

> Yep, to open it i do `/mnt/c/Program\ Files/Sublime\ Text/subl.exe .` > > About the console output, i get nothing:  What if you open a py file?

I can reproduce this but I didn't work under WSL2.

Fwiw, I tried this with VSCode + Pyright/Pylance emits the same error. Something like ``` LSP-pyright: venvPath \Ubuntu-20.04\home\didi\leaf\leaf-radio\.venv is not a valid directory. LSP-pyright: stubPath \Ubuntu-20.04\home\didi\leaf\leaf-radio\typings is not a valid...

> VSCode has this extension [marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-wsl) which allows you to seamlessy use the linux filesystem. Not open sourced so we have no idea what it does. Without its aid, VSCode...