Repository navigation
ipympl changes MPL backend on import #623
Description
Activity
Hmm I agree that that is a bad behavior. I suspect this can be changed depending on how the
%matplotlib ipymplmagic and matplotlib backend import works.Some relevant code paths from a quick check
The actual lines that cause the backend to be changed on import.
Lines 23 to 28 in 36ae86d
which are 8 years old and
nbextensionis no longer relevant so I'm pretty sure we can just remove that entirely. But would love to hear what @martinRenou thinks before doing thatAs a workaround for now you can try directly importing from
_versionIn [1]: from ipympl._version import version_info In [2]: version_info Out[2]: (0, 10, 0)
Reacted by Stefan Appelhoff
In mne-python (see above), we have a functionality called
sys_info, which gives us (among other things) the versions of all sorts of installed packages.For this reason, we also import ipympl.
At import time, ipympl actually changes the MPL backend.
Is this something that could be avoided? This change in backend was very surprising to us and it took an in-depth profiling to identify it as the cause of a massive memory leak in a pipeline that produced several plots on each iteration, never closing them due to the backend change.