On Sun, Feb 27, 2011 at 1:06 AM, Eric Firing <efir...@hawaii.edu> wrote:
> That's a good point. Until fairly recently, interactive behavior worked > across backends only via ipython magic, so I think the non-interactive > default had a solid historical rationale. Now, however, we could > probably make interactive mode the startup default for interactive > backends without causing any problems. I agree that this would be more > intuitive and more familiar to people coming from matlab. Probably right -- this was a design decision made early on when I did not see a good way around the problem that the idle drawing across backends now solves. There will probably be some unintended consequences of changing the default, but as long as we document it prominently and provide a way for people to change the behavior to the old wan in their rc, it is probably a good idea to make this change. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
