Skip to content
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

Install to current version of jupyterlab (2.1.1) not working #118

Open
jerri opened this issue May 3, 2020 · 2 comments
Open

Install to current version of jupyterlab (2.1.1) not working #118

jerri opened this issue May 3, 2020 · 2 comments

Comments

@jerri
Copy link

jerri commented May 3, 2020

I have a small script to install jupyter and jupyterlab into a virtual environment. After installing jupyterlab, I try to install jupytherlab-vim. This worked in the past, but right now I get the following error:

> jupyter labextension install jupyterlab_vim
An error occured.
ValueError: The extension "jupyterlab_vim" does not yet support the current version of JupyterLab.


Conflicting Dependencies:
JupyterLab              Extension      Package
>=2.1.1 <2.2.0          >=1.0.1 <2.0.0 @jupyterlab/application
>=2.1.1 <2.2.0          >=1.0.1 <2.0.0 @jupyterlab/notebook
See the log file for details:  /tmp/jupyterlab-debug-o2s9wxtj.log

I install jupyter and jupyterlab via pip inside the virtual environment. Am I doing something wrong? jupyterlab-vim is supposed to support 2.1.1, no?

jupyterlab-debug-o2s9wxtj.log

@jmerizia
Copy link

Sounds like there is active work to support JupyterLab 2.x. It's a fairly new release, so extensions are still working to catch up.

According to #115, until changes are merged, a temporary fix is to install from the forked repository with jupyter labextension install @axlair/jupyterlab_vim

@jerri
Copy link
Author

jerri commented Dec 2, 2021

Just for an update. I tested the install of jupyterlab_vim again with current version of jupiter. And it still fails. The only way to install it is via the way mentioned by jmerizia. Therefore it might make sense to document this properly in the READMEs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants