We talked about this on the phone at the end of day 1 scipy sprints when my brain was turning to mush.

The quandary (quagmire?) we are trying to get our selves out of is that

a) we want to use the standard IPython/jupyter protocols as much as possible
b) there is a long history of special casing things (on all sides) to "make it work"
c) attempts to do a) tend to run afoul of b)

The things we want to work in notebooks / jlab

fig=plt.figure()

fig,ax=plt.subplots()

should show the figure even though theFigure is not the last thing in the cell (so not a candidate for the automatic display) and the user has not explicitly displayed it. You could argue that this is counter to a) above, but there is a decade of user expectation on this. If we find a process to achieve this within the constraints of a) that lets us drop all of b) that can presumable this could be extend to other libraries that want to fabricate complicated widgets and have them implicitly shown.

fig=plt.figure()fig

This should show exactly once so that the implicit display from the first case and the automatic display from the second case do not conflict with each other.

fig# assuming this is defined in another cell

should also show the "correct" version of the Figure in the notebook.

Tangentially, we probably also want a clean way for ipympl / notebook to throw a snapshot of the current figure into the notebook. This can be very useful if you have a notebook that is progressively building a complex figure to get "snapshots" of the intermediate state. We are also using this to work around the issue with ipympl rendering a an empty figure when exported.

We also want to make sure that we do not render the figure N times (for example always including both a html and a png version which both have the png embedded) both for run time and payload size reasons (or find a way to manage the caching / data sharing).

Tools we have at our disposal

• the_repr_*_ methods on theFigure andcanvas objects
• post-execute hooks (well, pre-execute too, but that seems not useful for us)
• the ability to register higher-priority single-dispatch display logic with IPython / jupyter
• explicit calls to display

I think the question with this PR is not if it solves all of the problems, but if it moves us forward along any direction (which I think it does in the case of a no-pyplot workflow) and if it paints us into an API corner that we will not be able to get out of (which I don't think it does because this is the lowest priority code path and all of the current special-casing will still win).

@tacaswell I have confirmed that the following code cell renders a figuretwice in Jupyter Lab, but the new code for_repr_png_ in this PR is not called. It must be something else in IPython / matplotlib causing that, which is best left for another issue / PR.

import matplotlib.pyplot as pltfig = plt.figure()ax = fig.add_subplot()fig

To the best of my knowledge / testing, this PR meets@tacaswell's stated goal:

I think the question with this PR is not if it solves all of the problems, but if it moves us forward along any direction (which I think it does in the case of a no-pyplot workflow) and if it paints us into an API corner that we will not be able to get out of (which I don't think it does because this is the lowest priority code path and all of the current special-casing will still win).

For reference, the function we are checking for an attribute on ishttps://github.com/ipython/ipython/blob/8ad12b0f8fbb2af5386ab31972fbc9889c3d1eb4/IPython/core/pylabtools.py#L363-L419 which is called fromhttps://github.com/ipython/ipython/blob/8ad12b0f8fbb2af5386ab31972fbc9889c3d1eb4/IPython/core/interactiveshell.py#L3396-L3439 which is in turn called fromhttps://github.com/ipython/ipython/blob/8ad12b0f8fbb2af5386ab31972fbc9889c3d1eb4/IPython/core/magics/pylab.py#L47-L100 so what the condition is checking is "has the user typed%matplotlib (or otherwise calledip.shell.enable_matplotlib()?".

It looks like there is some figure-level registration athttps://github.com/ipython/ipython/blob/8ad12b0f8fbb2af5386ab31972fbc9889c3d1eb4/IPython/core/pylabtools.py#L209-L257

It looks like there is some figure-level registration atipython/ipython@8ad12b0/IPython/core/pylabtools.py#L209-L257

I'm happy to have a matplotlib version check there and do nothing if matplotlib.version >= whatever. I can even backport such a change to 7.x which is released monthly.

For further details, ipympl works because ipywidgets implements_ipython_display_ (in widgets < 8 and_repr_mimbundle_ in 8+) on the canvas class.

_repr_mimebundle_ /_ipython_display_, but I am having trouble sorting out how to force it to down-grade to a png (maybe because it does not know about it yet?)

Great job@bdice for picking this up!

This is probably an unpopular opinion, but I think there should be a clean split between ipython and matplotlib. As far as I know, matplotlib is the only library that gets special cased.

Seems it would be much simpler if users just had to placefig as the last line of a notebook cell.

Seems it would be much simpler if users just had to place fig as the last line of a notebook cell.

Do you mean always, or only if the%matplotlib magic has not been called?

This needs a rebase. It probably also needs a project manager...@tacaswell you are probably the best person to lead the charge on this?

I'm not sure how to help this move forward. I am going to close this as a stale PR, but feel free to upstream/rebase anything you want from here!