ipython/ipython — Issue #992: Interrupting certain matplotlib operations leaves the inline backend 'wedged'
Author: fperez
Created: 2011-11-11 07:42:58+00:00
State: open
Labels: prio-critical, type-bug

This is something I've only noticed on the notebook, though it likely also occurs with the qt console. If I interrupt a matplotlib rendering operation, quite often it becomes impossilbe to get any further plots to show up. Somewhere, we're holding state that isn't fully restored if the rendering operation is interrupted by the user.

Typing `%pylab inline` fixes it, but that's an arcane solution which also has the side-effect of re-importing all the pylab namespace on top of the user's interactive namespace.

I've had this bite me often enough lately to realize it will be a major usability headache for new users of the notebook, which is why I'm making it critical. I suspect it will be easy to fix once we have a look at our inline pylab code.