-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Support JupyterLab 2.0.0 - plotlywidget #2261
Support JupyterLab 2.0.0 - plotlywidget #2261
Conversation
/cc: @nicolaskruchten being the reviewer of #2245! |
Thanks @consideRatio ! I tried this last week and while it works in Jlab 2.x it breaks in 1.2... I filed an issue to discuss this over here jupyter-widgets/ipywidgets#2809 ... Are you able to install |
Ah thanks for looping me in @nicolaskruchten! I struggle to overview the situation still. Dependency overviewTo be able to install the latest version of plotlywidget on both JupyterLab 1 and 2, we need to avoid have conflicting dependencies making us request both for example jupyte-widgets/base of two different versions, but also not two different versions of jupyterlab core packages.
To test if this change make sense, I figure one would need to.
Then, do the same, but starting out by installing JupyterLab 2. |
Reproduce my test
Successful outcome for both JupyterLab 1 and 2 |
OK then! I guess the way I was testing it was not sufficiently isolated. I was downgrading JupyterLab from 2 to 1 in the same environment. Thanks for going all the way through all the right motions to make this work :) |
Yes, basically that's the idea. The lab manager will pull in the correct version of the base package, so you just need to allow either base package version, and the lab manager will pick the one that works with your jupyterlab version. This relies on JupyterLab correctly and completely deduplicating packages in the build process. |
OK this is lovely, thanks everyone for bearing with my bad testing practices and helping out, it's much-appreciated! I'm planning on pushing out another patch release tomorrow with this fix |
OK, so I built and published version 1.5.4-rc1 of JLab 1.2 test sequence
JLab 2.0 test sequence
|
Ah hang on, this might be because the version of the widget doesn't match what |
As in you want to investigate this a bit further and post results? |
Yes, sorry. I think that's what it was... I didn't realize just how coupled |
OK yes, if I set https://github.com/plotly/plotly.py/blob/master/packages/python/plotly/plotly/_widget_version.py to match the exact version including the |
Yeah, you're running into two different things:
|
Thanks for the extra info @jasongrout ! I'm new to the release process of Sorry for the multiple false alarms. |
@nicolaskruchten Thanks, but still no joy here :(
gives the below. I can't (I think) use a venv because I'm running in a jupyterhub container (I can't even work out how to restart jupyter lab without inadvertently killing the pod).
|
@jtlz2 there are newer versions of things out at this point, so locking into Here are versions of relevance: I note also that you got this error:
And that you had version 8.10.0 active, so even though you wrote |
I agree with @consideRatio: the core issue seems to be that this command is running under an outdated version of In addition, yesterday we released Plotly.py 4.6.0 and the corresponding extensions now share version numbers, so you'll likely want the extensions versioned 4.6.0 as well. |
See #2249 (comment)
Attempted fix for #2249, but not tested and mainly a suggestion without deep comprehension. This should had been part of #2245 if I had done it right from the start.