For some reason, we were encountering this bug even with ipympl 0.9.6 installed in the environment we were using. After restarting the kernel multiple times, we don't encounter the bug anymore - maybe a caching issue? Thanks!
Still getting the same error with matplitlib 3.10.3 and ipympl 0.9.7 on completely clean and uncached builds, don't think this can be should be closed yet.
Activity
ianthomas23 commented on Feb 21, 2025
This is a duplicate of #29337 and matplotlib/ipympl#575, it is already fixed in PR matplotlib/ipympl#577 and released in ipympl 0.9.6. Please update your version of ipympl.
lpilz commented on Feb 21, 2025
For some reason, we were encountering this bug even with ipympl 0.9.6 installed in the environment we were using. After restarting the kernel multiple times, we don't encounter the bug anymore - maybe a caching issue? Thanks!
T-Wainwright commented on Jul 21, 2025
Still getting the same error with matplitlib 3.10.3 and ipympl 0.9.7 on completely clean and uncached builds, don't think this can be should be closed yet.
dprotter commented on Aug 1, 2025
I am having the same issue with 3.10.3 / 0.9.7 on Ubuntu 24.04 in a fresh conda env. Had to roll back to 3.7.5 and 0.9.3 to get interactivity to work.
ianthomas23 commented on Aug 1, 2025
This has been identified as a problem in VSCode.
dprotter commented on Aug 1, 2025
a problem with the jupyter extension? if you have it handy, could you link to the bug report?
ianthomas23 commented on Aug 1, 2025
There is a discussion in #30337 with steps to reproduce the problem in VSCode whereas the problem does not occur in JupyterLab.