On Mon, Dec 10, 2012 at 2:45 AM, Phil Elson wrote:
> Hi Joe,
>
> Thanks for bringing this up, it is certainly valuable to highlight this on
> the mailinglist. As you say, the change is hard to spot and, I agree, makes
> library code supporting v1.1.1 and v1.2 harder than one would like.
> Typical
Paul,
Actually, I didn't realize that you had to change the backend in the
matplotlibrc file. Once I changed it to 'Qt4Agg', everything worked.
Thanks!
(to find out where your matplotlibrc file is:
"matplotlib.matplotlib_fname()" )
Tim
On Mon, Dec 10, 2012 at 2:34 PM, Timothy Duly wrote:
>
Paul,
I am using the "agg" backend:
In [1]: import matplotlib
In [2]: matplotlib.rcParams['backend']
Out[2]: 'agg'
I was able to switch it to the one you have:
In [12]: import matplotlib
In [13]: matplotlib.rcParams['backend'] = 'Qt4Agg'
but still a simple "plot(1,1)" resulted in no plot bei
On Mon, Dec 10, 2012 at 12:15 PM, Timothy Duly wrote:
> Hi,
>
> I recently upgraded to matplotlib v1.2.0 on my Linux machine. For some
> reason, plots are not appearing at all on my screen whenever I try to plot
> any routines.
>
> When I open the interpreter with "ipython --pylab" and do
>
> In
Hi,
I recently upgraded to matplotlib v1.2.0 on my Linux machine. For some
reason, plots are not appearing at all on my screen whenever I try to plot
any routines.
When I open the interpreter with "ipython --pylab" and do
In [1]: plot(1,1)
Out[1]: []
No plot shows up. This is somewhat strange
Hi Joe,
Thanks for bringing this up, it is certainly valuable to highlight this on
the mailinglist. As you say, the change is hard to spot and, I agree, makes
library code supporting v1.1.1 and v1.2 harder than one would like.
Typically, anything which is going to break core APIs (even slightly)
s
