-
Notifications
You must be signed in to change notification settings - Fork 950
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 to jupyterlab 4 and lumino 2 #3707
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for starting this!
"@lumino/coreutils": "^2.0.0-beta.0", | ||
"@lumino/messaging": "^2.0.0-beta.0", | ||
"@lumino/widgets": "^2.0.0-beta.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest being soft on the Lumino dependencies:
"@lumino/coreutils": "^2.0.0-beta.0", | |
"@lumino/messaging": "^2.0.0-beta.0", | |
"@lumino/widgets": "^2.0.0-beta.0", | |
"@lumino/coreutils": "^1.11.1 || ^2.0.0-beta.0", | |
"@lumino/messaging": "^1.10.1 || ^2.0.0-beta.0", | |
"@lumino/widgets": "^1.30.0 || ^2.0.0-beta.0", |
That way people won't get warnings in the JS console with JupyterLab 3.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, that would be the goal. I'd like first to get the CI green with more strict constraints on lumino.
Among the failed CI jobs, there is the Javascript one. Is CI main branch supposed to be 100% green?
|
@martinRenou I have pushed fixes and this PR still requests approval. Is this possible to simply have the CI run on each commit without asking approval? |
I have pushed more updates for the CI and the CI running in my fork is now better. There is still one failure related to galata usage, see the details here. @fcollonval may have an idea how to investigate this, probably related to galata API changes between 3.x and 4.x ?
|
@echarles the setup of galata in JLab 4 is changing (the helpers are loaded as a regular JupyterLab extension): https://github.com/jupyterlab/jupyterlab/tree/master/galata#launch-jupyterlab |
Thx for the link. I have tried to implement those changes in a simple extension without luck. Do you have a link to an extension depending on jupyterlab4 that runs galata tests? |
Maybe this PR that updated the cookiecutter? jupyterlab/extension-cookiecutter-ts#287 |
Suprised to see #3752. Can you sync? |
Jupyterlab 4.0.0 was release yesterday https://github.com/jupyterlab/jupyterlab/releases/tag/v4.0.0 and it seems a new version with this PR is needed to work with jupyterlab-4.0.0, correct ? Using conda, I am getting: |
@tarrade this has to do with the conda package itself which has a run constraint. It was resolved in conda-forge/jupyterlab_widgets-feedstock#26 and you will be able to install latest ipywidgets with JupyterLab 4 in ~1 hour. |
perfect, pb solved, thanks a lot |
Closing as replaced by #3752, I made sure to keep you as a committer as it was built upon your work. Thank you! |
Fixes #3700