How to make jupyterlab-lsp work with Jupyter Lab - Launching Example Server failed: Error: spawn pyls ENOENT

It might be a lame question, but I went through all the installation steps and still can’t get jupyterlab-lsp to work:

• extension was installed in jupyter lab
• I installed the python-language-server
• servers.yml file - is in the folder from where my virtual env starts and I launch jupyter lab
• before starting jupyter lab I run the following line but it results in this error:

node /Users/konrad/.local/share/virtualenvs/SharedEnv-r6sHwbPo/share/jupyter/lab/staging/node_modules/jsonrpc-ws-proxy/dist/server.js --port 3000 --languageServers servers.yml

What am I missing here?

[bollwyvl]

Pep8?

On Mon, Oct 28, 2019, 14:24 Konrad [e-mail] wrote:

Frankly not really, but let me share some light on what I’m doing:

• I’m managing my Python versions with pyenv and environments with pipenv
• If I understand correctly I need to try to resolve this problem in the specific environment I’m currently working in (called SharedEnv)

When I try installing pip8 or the other listed package I get the following information:

~/DS&ML/Python/SharedEnv master*

❯ pipenv install pip8

Installing pip8…

Adding pip8 to Pipfile’s [packages]…

✔ Installation Succeeded

Pipfile.lock (40d26d) out of date, updating to (f06529)…

Locking [dev-packages] dependencies…

Locking [packages] dependencies…

✘ Locking Failed!

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/resolver.py”, line 69, in resolve

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 726, in resolve_deps

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 480, in actually_resolve_deps

pipenv.exceptions.ResolutionFailure: resolved_tree = resolver.resolve()

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 395, in resolve

pipenv.exceptions.ResolutionFailure: raise ResolutionFailure(message=str(e))

pipenv.exceptions.ResolutionFailure: pipenv.exceptions.ResolutionFailure: ERROR: ERROR: Could not find a version that matches pip8

pipenv.exceptions.ResolutionFailure: No versions found

pipenv.exceptions.ResolutionFailure: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.

First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again.

Alternatively, you can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.

Hint: try $ pipenv lock --pre if it is a pre-release dependency.

ERROR: ERROR: Could not find a version that matches pip8

No versions found

Was https://pypi.org/simple reachable?

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 726, in resolve_deps

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 480, in actually_resolve_deps

pipenv.exceptions.ResolutionFailure: resolved_tree = resolver.resolve()

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 395, in resolve

pipenv.exceptions.ResolutionFailure: raise ResolutionFailure(message=str(e))

pipenv.exceptions.ResolutionFailure: pipenv.exceptions.ResolutionFailure: ERROR: ERROR: Could not find a version that matches pip8

pipenv.exceptions.ResolutionFailure: No versions found

pipenv.exceptions.ResolutionFailure: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.

First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again.

Alternatively, you can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.

Hint: try $ pipenv lock --pre if it is a pre-release dependency.

ERROR: ERROR: Could not find a version that matches pip8

No versions found

Was https://pypi.org/simple reachable?

~/DS&ML/Python/SharedEnv master* 5s

❯ pipenv install pycodestyle

Installing pycodestyle…

Adding pycodestyle to Pipfile’s [packages]…

✔ Installation Succeeded

Pipfile.lock (04d4b2) out of date, updating to (f06529)…

Locking [dev-packages] dependencies…

Locking [packages] dependencies…

✘ Locking Failed!

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/resolver.py”, line 69, in resolve

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 726, in resolve_deps

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 480, in actually_resolve_deps

pipenv.exceptions.ResolutionFailure: resolved_tree = resolver.resolve()

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 395, in resolve

pipenv.exceptions.ResolutionFailure: raise ResolutionFailure(message=str(e))

pipenv.exceptions.ResolutionFailure: pipenv.exceptions.ResolutionFailure: ERROR: ERROR: Could not find a version that matches pip8

pipenv.exceptions.ResolutionFailure: No versions found

pipenv.exceptions.ResolutionFailure: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.

First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again.

Alternatively, you can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.

Hint: try $ pipenv lock --pre if it is a pre-release dependency.

ERROR: ERROR: Could not find a version that matches pip8

No versions found

Was https://pypi.org/simple reachable?

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 726, in resolve_deps

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 480, in actually_resolve_deps

pipenv.exceptions.ResolutionFailure: resolved_tree = resolver.resolve()

pipenv.exceptions.ResolutionFailure: File “/usr/local/Cellar/pipenv/2018.11.26_2/libexec/lib/python3.7/site-packages/pipenv/utils.py”, line 395, in resolve

pipenv.exceptions.ResolutionFailure: raise ResolutionFailure(message=str(e))

pipenv.exceptions.ResolutionFailure: pipenv.exceptions.ResolutionFailure: ERROR: ERROR: Could not find a version that matches pip8

pipenv.exceptions.ResolutionFailure: No versions found

pipenv.exceptions.ResolutionFailure: Warning: Your dependencies could not be resolved. You likely have a mismatch in your sub-dependencies.

First try clearing your dependency cache with $ pipenv lock --clear, then try the original command again.

Alternatively, you can use $ pipenv install --skip-lock to bypass this mechanism, then run $ pipenv graph to inspect the situation.

Hint: try $ pipenv lock --pre if it is a pre-release dependency.

ERROR: ERROR: Could not find a version that matches pip8

No versions found

Was https://pypi.org/simple reachable?

None of the other recommended solutions that I came across sorted this out. Am I missing something obvious here?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/krassowski/jupyterlab-lsp/issues/63?email_source=notifications&email_token=AAALCRAD7XXIR7VXLKV732DQQ4U6VA5CNFSM4JCVW7CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECN5C7Q#issuecomment-547082622, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALCRBVPDQXE6Q3A436METQQ4U6VANCNFSM4JCVW7CA .

[bollwyvl]

Pyls also takes a ‘-d’ flag which may give more output.

Not to derail the conversation too much: This case makes me think we may wish to pass debug down from notebook to the built-in servers in the upcoming python proxy, e.g.

{ “language_servers”: { “python-language-server”: { “argv”: [“pyls”], “debug”: [“pyls”, “-d”] } }

For some of them, e.g. r, it might be… more complicated.

On Mon, Oct 21, 2019, 16:12 M. Krassowski [e-mail] wrote:

Hi @konradsemsch https://github.com/konradsemsch, thanks for checking out our extension. The problem on the screnshoot appears to be unrelated to the jupyterlab-lsp extension, but to the pyls language server installation. I googled “error spawn pyls enoent” and got quite a few results, including:

• AtomLinter/linter-pycodestyle#30 https://github.com/AtomLinter/linter-pycodestyle/issues/30

https://stackoverflow.com/questions/42088575/error-spawn-pycodestyle-enoent

There are proposed solutions (mostly based on installing pep8/uninstalling some other packages) which seem to have worked for dozens of people, so I hope that this should work for you as well. Please let us know if it helps.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/krassowski/jupyterlab-lsp/issues/63?email_source=notifications&email_token=AAALCREJJ7MBSLCNE6GKE4DQPYEJ5A5CNFSM4JCVW7CKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB3UI4A#issuecomment-544687216, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAALCRHIKAXAWEMEYWY5E5TQPYEJ5ANCNFSM4JCVW7CA .