Re: [Matplotlib-users] python v ipython problem in imshow()

2010-11-11 Thread Garry Willgoose
ear > with wx? > > Best, > --Michiel. > > --- On Thu, 11/11/10, Garry Willgoose > wrote: > >> From: Garry Willgoose >> Subject: Re: [Matplotlib-users] python v ipython problem in imshow() >> To: "Michiel de Hoon" >> Cc: "Garry Will

Re: [Matplotlib-users] python v ipython problem in imshow()

2010-11-11 Thread Michiel de Hoon
'import wx' after program > startup but it had set to WX by the time it got the place > where the plots were made. > > > I haven't been able to replicate this bug. With all > matplotlib versions > > I tried (including 0.99.0, 0.99.1., 0.99.1.1, > 0

Re: [Matplotlib-users] python v ipython problem in imshow()

2010-11-10 Thread Michiel de Hoon
chiel. --- On Wed, 11/10/10, John Hunter wrote: > From: John Hunter > Subject: Re: [Matplotlib-users] python v ipython problem in imshow() > To: "Michiel de Hoon" > Cc: "Garry Willgoose" , > matplotlib-users@lists.sourceforge.net > Date: Wednesday, November 10,

Re: [Matplotlib-users] python v ipython problem in imshow()

2010-11-10 Thread John Hunter
On Wed, Nov 10, 2010 at 9:48 AM, Michiel de Hoon wrote: > Garry, if the bug still exists in matplotlib 1.0 could you open a bug report > for it? I think Gary doesn't have easy access to 1.0. Here is the relevant example if anyone has 1.0 on macosx to test with http://matplotlib.sourceforge.

Re: [Matplotlib-users] python v ipython problem in imshow()

2010-11-10 Thread Michiel de Hoon
Garry, if the bug still exists in matplotlib 1.0 could you open a bug report for it? Thanks, --Michiel. --- On Wed, 11/10/10, John Hunter wrote: > From: John Hunter > Subject: Re: [Matplotlib-users] python v ipython problem in imshow() > To: "Garry Willgoose" , "M

Re: [Matplotlib-users] python v ipython problem in imshow()

2010-11-10 Thread John Hunter
On Wed, Nov 10, 2010 at 5:43 AM, Garry Willgoose wrote: > John, > > OK by looking at matplotlib.rcParams['backend'] I've been able to diagnose > this a little more. > > When the backend is  'WXAgg' everything looks fine. The axes have (0,0) where > you would expect and the data is plotted correc

Re: [Matplotlib-users] python v ipython problem in imshow()

2010-11-10 Thread Garry Willgoose
John, OK by looking at matplotlib.rcParams['backend'] I've been able to diagnose this a little more. When the backend is 'WXAgg' everything looks fine. The axes have (0,0) where you would expect and the data is plotted correctly. However, when the backend is 'MacOSX' the axes again have (0,0

Re: [Matplotlib-users] python v ipython problem in imshow()

2010-11-09 Thread John Hunter
On Tue, Nov 9, 2010 at 4:33 PM, Garry Willgoose wrote: > I'm using the following code to plot some grided data > >        fig1=pylab.figure() >        contents1=fig1.add_subplot(111) >        stuff=contents1.imshow(mydata,origin='lower',aspect='equal') > > and I find that if I launch the code with

[Matplotlib-users] python v ipython problem in imshow()

2010-11-09 Thread Garry Willgoose
I'm using the following code to plot some grided data fig1=pylab.figure() contents1=fig1.add_subplot(111) stuff=contents1.imshow(mydata,origin='lower',aspect='equal') and I find that if I launch the code with 'ipython' the data looks as expected but if I use 'python' then