Skip to content
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

ipywidgets-6.0.0.rc2 doesnt behave as expected in Sage. #1161

Closed
EmmanuelCharpentier opened this issue Feb 25, 2017 · 3 comments
Closed

ipywidgets-6.0.0.rc2 doesnt behave as expected in Sage. #1161

EmmanuelCharpentier opened this issue Feb 25, 2017 · 3 comments
Labels
resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Milestone

Comments

@EmmanuelCharpentier
Copy link

This is related to Sage's ticket #21267. The ticket's author ported pywidgets-6.0.0.rc2 and widgetsnbextension-2.0.0rc1 to Sage, and was able to create Sage "interacts" (i. e. interactive plots using Sage-compatible widgets) in a Jupyter notebook using Sage's kernel.

Trying to reproduce is results, I merged his tree in my Sage installation, with no errors. However, When trying to reproduce Sage documentation examples (see here), I obtained only static graphs reflecting the default values of the widgets, and no widgets at all.

Furthermore, tje following message was printed in the terminal window from which Sage was launched (Sage launches its browser itself) :

[IPKernelApp] WARNING | The installed widget Javascript is the wrong version. It must satisfy the semver range ~2.1.0.

The ticket's author thinks that :

This is most likely not Sage-related, so please report this issue upstream to ipywidgets

Which I do. I tried to empty the caches of both Firefox and Chrimium, to no avail...

A (likely unrelated) information : Sages starts Firefox in order to display its worksheet, even when it is lainched with the "SAGE_BROWSER=chromium" environment variable ; this is abnormal...

HTH,

@jdemeyer
Copy link
Contributor

jdemeyer commented Mar 1, 2017

This is caused by having two installations of ipywidgets: one system-wide and one within Sage. Somehow ipywidgets does not pick up the "correct" version of the javascript in this case.

@jasongrout
Copy link
Member

Is this resolved?

This sounds like it may be a problem with the notebook extension mechanism, then - the extension mechanism is confusing and error-prone. It sounds like we should close this and note yet another reason to implement something like jupyter/notebook#1706.

@jdemeyer
Copy link
Contributor

It's not resolved but I agree that it's not an ipywidgets issue.

The problem turned out to be conflicting installations of ipywidgets (one system-wide and one user install).

@jasongrout jasongrout added this to the 6.0 milestone Apr 8, 2017
@github-actions github-actions bot added the resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Feb 14, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

No branches or pull requests

3 participants