Thanks. This has helped me isolate the problem to be some interplay
between the Agg backend and usetex being true.
With usetex turned on,
$ python examples/pylab_examples/simple_plot.py --verbose-debug > run_agg.out
fails to produce a plot. When usetex is turned off, the plot is produced.
With usetex turned on,
$ python examples/pylab_examples/simple_plot.py -dWXAgg
--verbose-debug > run_wxagg.out
correctly produces a plot. When usetex is turned off, the plot is
also produced.
Before updating, I never explicitly declared a backend (so I assume it
was using Agg), and I was always able to plot with usetex turned on.
I've attached my build.out and run.out (for both of the above cases
with usetex turned out). How can I further troubleshoot this? I have
a workaround now, but I'd like to understand what the problem is.
On Thu, Jun 12, 2008 at 2:47 PM, John Hunter <jdh2358@...149...> wrote:
On Thu, Jun 12, 2008 at 4:19 PM, T J <tjhnson@...149...> wrote:
I just updated my version of matplotlib to r5496, and now when I type
show(), nothing happens. What could have gone wrong? Sorry if this is
simple. I've attached a log of the installation.
With usetex turned on,
$ python examples/pylab_examples/simple_plot.py --verbose-debug > run_agg.out
fails to produce a plot. When usetex is turned off, the plot is produced.
If that is the case, then perhaps there has been a change. I never
specified a backend before, so I was using the default. With this
default, I was able to plot with usetex enabled.
···
On Thu, Jun 12, 2008 at 3:50 PM, Darren Dale <darren.dale@...143...> wrote:
On Thursday 12 June 2008 6:36:16 pm T J wrote:
Sorry, quick clarification:
With usetex enabled,
GTK will not plot
I don't think the gtk backend has ever supported usetex. Only the various Agg
backends, postscript, and pdf backends support ustex.