well it hasn't caused me any crashes yet so far as I can tell. Other naughty
things I do cause crashes, though.
On Thu, Aug 21, 2008 at 8:03 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 21, 2008 at 4:58 PM, Darren Dale <[EMAIL PROTECTED]> wrote:
>
>> On Thursday 21 August 2008 17:36:50 E
On Thu, Aug 21, 2008 at 4:58 PM, Darren Dale <[EMAIL PROTECTED]> wrote:
> On Thursday 21 August 2008 17:36:50 Eric Firing wrote:> Jack Sankey wrote:
> > > pylab.gcf().clear(); pylab.show() # nothing happens
> >
> > With interactive mode off, in a script, show() should never be called
> > more than
On Thursday 21 August 2008 17:36:50 Eric Firing wrote:
> Jack Sankey wrote:
> > pylab.gcf().clear(); pylab.show() # nothing happens
>
> With interactive mode off, in a script, show() should never be called
> more than once; it should be the last plot-related line of the script.
I thought we suppor
Thanks Eric,
I may be doing things a little bit weird since I've been with matplotlib for
many years. I did two things that fixed my problem: I wiped python25 out
completely and install enthought (with an older pylab). During the wipe I
noticed an extra pythonw running in the task manager that I h
Jack Sankey wrote:
> I'm not sure if this is a matplotlib issue or what, but all of a sudden
> I was not able to do gca() or gcf() correctly.
>
> A simple command-line on pyshell (using wxAgg backend) went like this:
I'm not familiar with pyshell, but evidently it is turning interactive
mode on,
I'm not sure if this is a matplotlib issue or what, but all of a sudden I
was not able to do gca() or gcf() correctly.
A simple command-line on pyshell (using wxAgg backend) went like this:
import pylab
pylab.plot([1,2,1]) # figure pops up
pylab.gca().clear(); pylab.show() # nothing happens
pylab
