This is fantastic, I hope it fixes the crashes I've been
> having which I finally seem to have traced down to
> matplotlib freeing images ...
It probably won't fix it, because I didn't do anything that should
effect memory handling, but we'll keep our fingers crossed. If you
continue to experience problems and have any more information about
the bug, pass it on.
> One question though:
> FigureManagerBase's add_axes, add_subplot and
> set_current_axes methods have been removed (and this
> doesn't seem to be mentioned in API_CHANGES). What should I
> do to replace a call to add_axes?
Sorry, I got lazy. I updated API_CHANGES on the web. I thought only
the GUI backends were using add_subplot, set_current_axes, etc, and I
ported the changes to all the GUIs. See my last post
for more information.
Basically the figure class itself maintains the current axes - the
motivation for the changes is in the post above. Call fig.add_axes,
fig.add_subplot, fig.gca and fig.sca (set_current_axes).
Hope this helps,