WIP : draft of replacement for pyplot #3587
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pyplot_nng replaces most of pyplot plotting functions, a few
things (like plt.subplots and the other axes/figure generation
functions) need to be
interactive gives a auto-redraw wrapper for explicitly using axes, but
forces you through a functional interface rather than the OO interface.
This a result of http://thread.gmane.org/gmane.comp.python.matplotlib.devel/12999
On one hand, this is a huge API change (but it can be done breaking back-compatibility as slowly as we want), but I think this will greatly simplify things going forward and solve the pyplot vs OO issues replacing both with a more functional approach (we still need to work out where the edges are, is it
set_yscale(ax, 'log')
,ax.yscale('log')
,ax.set_yscale('log')
orax.yscale = 'log'
). The pyplot/interactive repl interface is an automatic wrapping of the functions to handle the global state and automatic re-drawing and the functions take the place of the OO in scripts and user developed functions.This would also let us sort the plotting functions in to modules which might help with the documentation issues.
cc @efiring