To overhauling all of the default colors, I think that is still in the cards, but some one who is not me needs to drive that.
The goal of pulling pyplot out of backend_bases is exactly that, to be able to do everything using the OO interface in a convenient way.
On Sun Feb 08 2015 at 4:50:51 PM Todd <toddrjen@…149…> wrote:
On Feb 8, 2015 1:13 AM, “Thomas Caswell” <tcaswell@…149…> wrote:
To start with, the 2.0 release is pending a choice of new default color map. I think that when we pick that we should cut 2.0 off of the last release and then the next minor release turns into 2.1. If we want to do other breaking changes we will just do a 3.0 when that happens. It makes sense to me to bundle default color changes as one set of breaking changes and code API changes as another.
I thought there was going to be a complete overhaul of the default theme? Has that idea been abandoned?
making OO interface easier to use interactively (if interactive, auto-redraw at sensible time)
pull the pyplot state machine out of backend_bases and expose the figure_manager classes
Do either of these mean that it will be possible to use the OO interface without needing to go through pyplot?
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/_______________________________________________
Matplotlib-devel mailing list