Closed GorgiAstro closed 10 months ago
I do not think JupyterLab 3.x plugins are compatible with 4.x. That means we need to migrate or recreate it to support 4.x, and it's not a trivial task or easy fix. I think I can contribute it but I'm afraid it's not a priority in this phase.
Currently, we are actually only supporting JupyterLab 2.x. It looks like we should be able to move to JupyterLab 3.x without too much trouble. However, as noted by @himi, moving to JupyterLab 3.x is likely more effort than we have resources for right now.
@GorgiAstro, If you would like to discuss this further with the community, please start a conversation in the SysML v2 Release Google Group.
No, this is still problematic. I'm trying to install the SysML V2 jupyterlab prototype on my laptop, and hitting serious compatibility issues during install.
First, the install.bat file attempts to downgrade Jupyter lab at this line:
call conda install "jupyter-sysml-kernel=%SYSML_VERSION%" python=3. jupyterlab=2. graphviz=2. nodejs=14. -c conda-forge -y || goto:error
This downgrades jupyterlab & server to 2.3.2 & 1.2.0
Downscript, this warning gets raised: Conflicting Dependencies: JupyterLab Extension Package
=4.1.5 <4.2.0 >=2.0.0 <3.0.0 @jupyterlab/application
Not sure how to proceed.
Thanks, -Jeff
It looks like jupyterlab version >= 4 does not manage to build the jupyterlab-sysml extension.
I just tested with my old jupyterlab version 3.6.6 , it built the extension successfully. After upgrading to version 4.0.10 however, I get the following error when jupyterlab tries to build the extension (this is from the jupyterlab debug log):
Environment: