dev-install "@jupyter-widgets/jupyterlab-manager@0.39.1" is not compatible with the current JupyterLab
See original GitHub issuehey everyone!
I am following these steps described here https://github.com/jupyter-widgets/ipywidgets/blob/master/docs/source/dev_install.md#installing-with-conda … but with no sucess.
This is the error:
jupyter-widgets-jupyterlab-manager-0.39.1.tgz
Errored, use --debug for full output:
ValueError:
"@jupyter-widgets/jupyterlab-manager@0.39.1" is not compatible with the current JupyterLab
Conflicting Dependencies:
JupyterLab Extension Package
>=0.19.1 <0.20.0 >=1.0.0-alpha.3 <2.0.0@jupyterlab/application
>=0.19.2 <0.20.0 >=1.0.0-alpha.4 <2.0.0@jupyterlab/notebook
>=0.19.1 <0.20.0 >=1.0.0-alpha.3 <2.0.0@jupyterlab/rendermime
any idea?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:13 (12 by maintainers)
Top Results From Across the Web
How to get ipywidgets working in Jupyter Lab? - Stack Overflow
JupyterLab now prefers a model where arbitrary javascript is no longer allowed ... is not compatible with the current JupyterLab Conflicting ...
Read more >Installation — JupyterLab 3.6.0b0 documentation
JupyterLab can be installed using conda , mamba , pip , pipenv or docker . ... 14 do not support CSS Variables, and...
Read more >JupyterLab - PyPI
The current JupyterLab releases are suitable for general usage, and the extension APIs ... If you encounter an error like "Command 'jupyter' not...
Read more >JupyterLab 3.0 is released - Jupyter Blog
0 with pip or conda to automatically enable ipywidgets in both the classic Jupyter Notebook and in JupyterLab 3.0 — no extra installation...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just adjusted the tags so that latest points to 0.38.1, and next points to 0.39.1. That should resolve this issue here. Thanks again for filing this issue!
Good point. Or change the npm tags to point
latest
to the version that works with jlab 0.35, andnext
to point to the prerelease version.