[IPython-dev] 0.10.2.rc1 ready for testing.

[Fernando Perez]

Hey Paul,

On Sun, Mar 13, 2011 at 4:13 AM, Paul Ivanov <pivanov314 at gmail.com> wrote:
> Fernando Perez, on 2011-03-12 23:06,  wrote:
>> The nasty gtk blocking problem we had is, to the best of my knowledge,
>> fully fixed here (thanks to P. Ivanov, M. Voorhies and others who
>> helped!).
>
> speaking of which, I feel like I'm going cross-eyed with this bug,
> so maybe this isn't a problem and should be considered user error
> (I'll sleep on it before I look at what behavior should be
> expected from matplotlib when the rcParam['interactive'] is set
> to False), but the following short little script screws
> up GTK threading, for me.
>
> -----
> import matplotlib
> matplotlib.use("GTKAgg")
> import matplotlib.pyplot as plt
> #plt.interactive(True) # uncomment to fix
> plt.plot(range(10))
> plt.show() # looks fine
> plt.close()
> plt.plot([2,1,2]) # this will timeout
> plt.show() # grey window, no toolbar drawn
> -----
>
> I think in our testing, Mark and I only checked if the first
> figure worked, not the second. The above script doesn't seem to
> cause issues if called with -pylab (which makes me think the
> above just falls under user error) or when using just -wthread
> with matplotlib.use("WXAgg").

Keep in mind that what you describe is perfectly OK: we never expected
the above to work without -pylab.  So as long as things do work
correctly when people do call -pylab, without any blocking or other
issues, we're in the clear.

Does that make sense?

f