matplotlib / matplotlib/ipympl
JupyterLab - sharing kernels breaks ipympl
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 1.7k
- Forks
- 234
- PR merge metrics
- No merged PRs in 30d
Description
## Describe the issue
If I have two notebooks open in jupyterlab, with the kernel of the second chosen as the kernel of the first (using jupyterlab gui kernel dropdown menu -> change kernel and making a choice from "use kernel from preferred session" and selecting notebook1.ipynb). If I try and use ipympl in this second notebook I get the "Error displaying widget: model not found" error. But ipympl works perfectly if I select the second (and original) kernel for the second notebook.
I'm doing this kernel sharing because I am using jupyterlab to control my experiment and only once instance of the hardware control code can be loaded. My idea is that my various measurements will be in separate jupyter notebooks but control a single kernel (where the hardware is defined). So far this idea works fine except for ipympl, I can still plot with `%matplotlib inline`.
I have tested this in a fresh conda environment with the latest versions of everything (AFAIK).
## Versions
```
3.9.5 (default, May 18 2021, 14:42:02) [MSC v.1916 64 bit (AMD64)]
ipympl version: 0.7.0
jupyter core : 4.7.1
jupyter-notebook : 6.4.0
qtconsole : 5.0.3
ipython : 7.22.0
ipykernel : 5.3.4
jupyter client : 6.1.12
jupyter lab : 3.0.16
nbconvert : 6.0.7
ipywidgets : 7.6.3
nbformat : 5.1.3
traitlets : 5.0.5
Known nbextensions:
config dir: C:\Users\monnvadmin\anaconda3\envs\control\etc\jupyter\nbconfig
notebook section
jupyter-matplotlib/extension enabled
- Validating: ok
jupyter-js-widgets/extension enabled
- Validating: ok
JupyterLab v3.0.16
C:\Users\monnvadmin\anaconda3\envs\control\share\jupyter\labextensions
jupyter-matplotlib v0.9.0 enabled ok
@jupyter-widgets/jupyterlab-manager v3.0.0 enabled ok (python, jupyterlab_widgets)
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in JupyterLab 3.0.16 by sharing notebook1.ipynb's kernel through the kernel dropdown, then use ipympl in the second notebook and observe the widget model error. Compare this with the working separate-kernel case; done means ipympl displays correctly when kernels are shared without the reported error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- backend, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100