-
Notifications
You must be signed in to change notification settings - Fork 317
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
Update for jupyterlab 3 #779
Comments
Yes the master should follow the latest major JupyterLab. And for older JupyterLab, the branches We should also think what is required to reach 1.x => but not in an issue rather linking issue to milestone. |
With 3.0 I get |
This issue is not closed, and the corresponding PR (#818) has not been merged, so it's probably reasonable to assume that it hasn't been updated for 3.0 yet? |
It is not yet release for JupyterLab 3 as it requires first nbdime to be released on it. If you want to be notified when it will be released, you can subscribe to this issue in the right panel. |
Hello, |
Hello, When will you support the jupyterlab 3? Best |
Is there any ETA on this? It is a serious limitation for us a we use multiple plugins that require Lab v3 |
I'm reopening as the current status is beta for JLab3 (waiting for final release of nbdime). |
A beta version has been released for JupyterLab 3. To test it you can install it with:
CC @ajbozarth |
I think that for jupyterlab 3 the command should be: there's an extra space in |
Thank you @ianhi I am using jupyterhub, and have this problem: I checked using jupyter server extension list, and jupyter labextension list to check, looks everything fine. If I run jupyterlab directly on the server, and everything is fine including git operation as I tried. Anyone has any idea about this issue? Thank you. |
Also having this issue. Any suggestions? |
With JupyterHub and JupyterLab 3, the setting to start JupyterLab has changed - see the documentation.
|
My default user interface is Jupyterlab. Would this have anything to do with nbdime? I'm using the newest beta version 3.0.0.b1 |
@JessicaBarh , FYI, I downgraded jupyterlab to 2.x, and also git. Everything goes back normal. |
@JessicaBarh what about this one: https://github.com/krassowski/jupyterlab-lsp/issues/375#issuecomment-761078622 I think predicted it will affect jupyterlab-git users here: jupyterlab/jupyterlab#9616 (comment) ;) But, seriously now, is there a way we could help JupyterHub to release a version defaulting to |
What's the timeline on releasing 0.30.0 with the lab 3 support? |
We need nbdime for JLab3 to get out of beta. I think what is holding nbdime is the broken tests if you want to help with that. |
I am facing the exact same issue as @hawlcat and @JessicaBarh running jupyterhub and installing in notebook server using:
Is there a workaround that doesn't require downgrading? |
@william-sheldon @hawlcat I got it working using |
This issue has been mentioned on Jupyter Community Forum. There might be relevant details there: https://discourse.jupyter.org/t/jupyterlab-git-in-jupyter-hub/8108/2 |
nbdime-3.0.0 is out |
The first version supporting JupyterLab 3 (jupyterlab-git==0.30.0) has been released on pypi.org. conda release will follow soon. |
edit - Install jupyterlab-git beta: Jupyterlab-git has a beta release which you can install with:
Description
Jupyterlab version 3 is nearly upon us (rc this week I think?).
The update to jlab3 may be as simple as running:
python -m jupyterlab.upgrade_extension .
but what should be done w.r.t branches on this repo? Should master track jlab 3 and then create a0.2x.y
branch for bugfixes for jlab2?The text was updated successfully, but these errors were encountered: