Re: [matplotlib-devel] pyplot commands appear to ignore interactive status

2011-02-07 Thread Mike Kaufman
On 2/7/11 10:30 PM, Benjamin Root wrote: > > The behavior in gtk and other backends is the designed/intended > behavior. macosx backend is actually the odd-man out because it was > coded to only work in one of those modes. > > Maybe we should emit a warning when macosx backend is used when > inter

Re: [matplotlib-devel] pyplot commands appear to ignore interactive status

2011-02-07 Thread Benjamin Root
On Mon, Feb 7, 2011 at 9:17 PM, Mike Kaufman wrote: > On 2/7/11 9:28 PM, Eric Firing wrote: > > >>> Which backend are you using and using which OS? > >> > >> Good question. Snow Leopard and the MacOSX backend. If I use the Gtk > > > > This is a known bug in the MacOSX backend. > > > >> backend th

Re: [matplotlib-devel] pyplot commands appear to ignore interactive status

2011-02-07 Thread Mike Kaufman
On 2/7/11 9:28 PM, Eric Firing wrote: >>> Which backend are you using and using which OS? >> >> Good question. Snow Leopard and the MacOSX backend. If I use the Gtk > > This is a known bug in the MacOSX backend. > >> backend this bug does _not_ occur (though I have to use the plt.show() >> command

Re: [matplotlib-devel] pyplot commands appear to ignore interactive status

2011-02-07 Thread Eric Firing
On 02/07/2011 04:13 PM, Mike Kaufman wrote: > On 2/7/11 9:02 PM, Benjamin Root wrote: >> On Mon, Feb 7, 2011 at 7:20 PM, Mike Kaufman> > wrote: >> >> >> using a recent svn (r8900), I've noticed that after starting from a >> regular python shell: >> >> >>>

Re: [matplotlib-devel] pyplot commands appear to ignore interactive status

2011-02-07 Thread Mike Kaufman
On 2/7/11 9:02 PM, Benjamin Root wrote: > On Mon, Feb 7, 2011 at 7:20 PM, Mike Kaufman > wrote: > > > using a recent svn (r8900), I've noticed that after starting from a > regular python shell: > > >>> import matplotlib.pyplot as plt > >>> plt.isinteracti

Re: [matplotlib-devel] pyplot commands appear to ignore interactive status

2011-02-07 Thread Benjamin Root
On Mon, Feb 7, 2011 at 7:20 PM, Mike Kaufman wrote: > > using a recent svn (r8900), I've noticed that after starting from a > regular python shell: > > >>> import matplotlib.pyplot as plt > >>> plt.isinteractive() > False > >>> plt.plot([1,2,3],[1,3,2]) > [] > >>> plt.plot([1,2,3],[1,2,3]) >

[matplotlib-devel] pyplot commands appear to ignore interactive status

2011-02-07 Thread Mike Kaufman
using a recent svn (r8900), I've noticed that after starting from a regular python shell: >>> import matplotlib.pyplot as plt >>> plt.isinteractive() False >>> plt.plot([1,2,3],[1,3,2]) [] >>> plt.plot([1,2,3],[1,2,3]) [] # plt.draw() is not required, the figure pops up # and both plots are