Re: [matplotlib-devel] New flags in IPython, of interest to matplotlib users

2007-12-12 Thread Fernando Perez
On Dec 12, 2007 7:16 AM, Paul Kienzle <[EMAIL PROTECTED]> wrote: > I'm curious about the term 'threading backend'. > > Recently I posted a question about how to handle slow plots, suggesting > that the backend canvas have an isabort() method so that the renderer > can stop what it is doing and post

Re: [matplotlib-devel] New flags in IPython, of interest to matplotlib users

2007-12-12 Thread Paul Kienzle
I'm curious about the term 'threading backend'. Recently I posted a question about how to handle slow plots, suggesting that the backend canvas have an isabort() method so that the renderer can stop what it is doing and post the current bitmap as it stands. This is to support interactive operation

Re: [matplotlib-devel] New flags in IPython, of interest to matplotlib users

2007-12-12 Thread Gael Varoquaux
On Wed, Dec 12, 2007 at 01:36:01AM -0700, Fernando Perez wrote: > You can now do this as well: > tlon[~]> ipython -wthread -pylab --nobanner > In [1]: matplotlib.rcParams['backend'] > Out[1]: 'WXAgg' Hurray, mayavi and pylab can now easily live together. Thanks heaps Fernando. Gaƫl --

[matplotlib-devel] New flags in IPython, of interest to matplotlib users

2007-12-12 Thread Fernando Perez
Hi all, This was posted to the ipython-dev list, but since it's specifically for MPL, I figured the cross-list spam would be forgiven. In IPython SVN, I just added the ability to manually control the pylab threading backend choice directly from the command line. So for example if by default you