-
Notifications
You must be signed in to change notification settings - Fork 446
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
[BUG] Ipywidgets package update (8.0.1) broke latest Sparkmagic 0.20.0 #769
Comments
For context: ipywidgets 8.0 was released yesterday, which is a major version upgrade with breaking changes. From the above error, it looks like this change in ipywidgets 8 is affecting you:
From the looks of it, you may need to just update line 49 below:
My guess is that options_x_view is a dictionary (using a dictionary there has been deprecated for years), and should be converted to a list of values or a list of (label, value) tuples. I think you can change it to |
Or it looks like you can define options_x_view as: options_x_view = [(text(i), text(i)) for i in self.df.columns]
options_x_view.append(("-", None))
|
I worked around by installing this after sparkmagic==0.20.0:
Not sure about the 7.7.x, I had mixed results during the day, they were obviously altered. |
FYI, with JupyterLab 3.x, if JupyterLab and the kernel are in the same environment, you don't need to do both the Also, if you install ipywidgets 7.7.2, you'll get (a) some bugfixes in 7.7.1, as well as (b) the updated jupyterlab_widgets dependency on the correct version of jupyterlab_widgets. But yes, it's always a good idea to pin dependencies exactly (or at least to the minor version) for reproducibility. tldr; if your jupyterlab and kernel are in the same environment, you should be able to do
to pin dependencies exactly to ipywidgets 7. |
Lates version was fine couple days ago and broke because of Ipywidgets probably doing a major non-backward compatible change
I see in requirements.txt that SparkMagic constraints are ipywidgets>5.0.0
Here's what happen after the Livy session is loaded up:
Still investigating.
The text was updated successfully, but these errors were encountered: