I'm using a pyenv 3.9.2 set up now with no local .venv, .env.
(1) The server isnt automatically installed - I need to manually run the install command lsp-install-server and select mspyls
(2) Server falls over if lsp-python-ms-parse-dot-env-enabled` is true.
I did some debugging and the issue is that lsp-python-ms--extra-init-params calls lsp-python-ms--workspace-root (since no workspace passed in) which in turn calls lsp-workspace-root which returns nil despite it being a projectile project.
This is with lsp auto guess root set to t :- when nil it says the project is blacklisted (its not).
LSP :: main.py not in project or it is blacklisted.
There is a .projectile in the directory.
Modifying lsp-python-ms--workspace-root to use lsp--suggest-project-root solved the issue but I have no idea of the knock on effects. Bottom line is lsp-workspace root doesn't use lsp-auto-guess-root to correctly spot a projectile root and that in combination with the lsp-python-ms--workspace-root "cond" statement (it returns the nil returned by lsp-worskapce root) means it fails to identify the project root.
I'm using a pyenv 3.9.2 set up now with no local .venv, .env.
(1) The server isnt automatically installed - I need to manually run the install command lsp-install-server and select mspyls (2) Server falls over if lsp-python-ms-parse-dot-env-enabled` is true.
My working setup:-
When lsp-python-ms-parse-dot-env-enabled is set to t I get the backtrace attached. Snippet:-
backtrace.txt
EDIT:
I did some debugging and the issue is that lsp-python-ms--extra-init-params calls lsp-python-ms--workspace-root (since no workspace passed in) which in turn calls lsp-workspace-root which returns nil despite it being a projectile project.
This is with lsp auto guess root set to t :- when nil it says the project is blacklisted (its not).
There is a .projectile in the directory.
Modifying lsp-python-ms--workspace-root to use lsp--suggest-project-root solved the issue but I have no idea of the knock on effects. Bottom line is lsp-workspace root doesn't use lsp-auto-guess-root to correctly spot a projectile root and that in combination with the lsp-python-ms--workspace-root "cond" statement (it returns the nil returned by lsp-worskapce root) means it fails to identify the project root.