You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jupyter LSP support has two components. A frontend component and a server component, jupyter-lsp.
I have tried, but I cannot get jupyter-lsp to load up in a server created by jupyterWith; even if I do something hacky to get the frontend component loaded up.
What's the right way to get LSP working?
Possible solution
No response
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Created a new folder my-project/kernels/custom-python for the new kernel.
Created a default.nix file in there with the following.
{name,availableKernels,extraArgs,}:
availableKernels.python{projectDir=./.;displayName="Python with jupyterlab-lsp";name="python-with-jupyterlab-lsp";}
Created a pyproject.toml file with the following.
[tool.poetry]
name = "jupyter-nix-kernel-ipython"version = "0.1.0"description = ""authors = []
[tool.poetry.dependencies]
python = "^3.9"ipykernel = "^6.15.0"jupyterlab-lsp = "^3.10.2"python-lsp-server = {extras = ["all"], version = "^1.7.0"}
[tool.poetry.dev-dependencies]
# build systems for dependencieshatchling = "^1.3.1"
[build-system]
requires = ["poetry-core>=1.0.0"]
build-backend = "poetry.core.masonry.api"
lock the dependencies with poetry lock
Run nix run at the top level.
However, after I tried that I ran into an infinite recursion error similar to nix-community/poetry2nix#750.
I tried adding some overrides but that created new problems.
What's missing?
Jupyter LSP support has two components. A frontend component and a server component, jupyter-lsp.
I have tried, but I cannot get jupyter-lsp to load up in a server created by jupyterWith; even if I do something hacky to get the frontend component loaded up.
What's the right way to get LSP working?
Possible solution
No response
Alternatives
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: