pyplot-OO convergence

As a follow up to this following things are in master/in the works:

- auto-redraw on OO mutation is merged and will be in 1.5
- There is a draft implementation of using traitlets to capture artist
properties in the works. Still many details that need to be worked out
there, but there is a plausible path and we have the support of the IPython
folks in this. In addition to cleaning up the API this will also provide
use with an easy path to figure serialization.
- some of the introspection issues can be addressed in python 3.3+ with
Signature. That is something I plan to push on going forward



On Mon, Sep 29, 2014 at 7:34 AM Todd <toddrjen at> wrote:

On Sun, Sep 28, 2014 at 7:52 PM, Eric Firing <efiring at> wrote:

Regarding Matlab: it is justly popular for many reasons. It is
relatively easy to learn both by design and because of its consistent
high-quality documentation. Matplotlib's success has resulted in large
measure from its pyplot layer, which can shield learners and users from
mpl's complexity, which allows learners to build on their Matlab
knowledge, and which is particularly well suited to quick interactive
data exploration. The problem with the Matlab/pyplot approach is that
it doesn't scale well, so we see a chorus of advice along the lines of
"don't use pyplot except for subplots() and show(); use the nice,
explicit OO interface for everything else". But at present, this
doesn't work well, because the OO approach is not interactive enough,
and using the getters and setters is clumsy when typing at the
console--in demonstrating, teaching, learning, and exploring
interactively, every keystroke counts!

Matlab is actually slowly trying to transition to an OO-style interface of
their own. It has taken a LONG time, though.

Slashdot TV. Videos for Nerds. Stuff that Matters.
Matplotlib-devel mailing list
Matplotlib-devel at

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>