Control of thread/program not returning to ipython after creating a plot.

Hi,

I was wondering if you ever found a solution to this problem ?

I have the exact same issue with GTK (Agg or cairo) and WX backends
... I'm also under gentoo using ipython-0.10.1 and matplotlib-1.0.0
I don't have the warnings you have but same behavior, I have to call
show (if I don't a blank 'frozen' window is all that appears) but then
the ipython doesn't have control anymore.

Cheers,

   Sylvain

It is very possible that this problem was fixed shortly after the 1.0.0 release. Another possibility is that ipython might be causing an issue where it is loading some older matplotlib codes before the rest of matplotlib 1.0.0 is loaded (I have seen this happen once).

You can test for this theory by seeing if you have the same problem when using the regular python shell. If not, then it is likely to be a problem with ipython. If you do have the same problem in regular python, then the problem is with matplotlib and you will need to build the latest from svn.

Ben Root

···

On Sun, Dec 19, 2010 at 3:34 AM, Sylvain Munaut <246tnt@…287…> wrote:

Hi,

I was wondering if you ever found a solution to this problem ?

I have the exact same issue with GTK (Agg or cairo) and WX backends

… I’m also under gentoo using ipython-0.10.1 and matplotlib-1.0.0

I don’t have the warnings you have but same behavior, I have to call

show (if I don’t a blank ‘frozen’ window is all that appears) but then

the ipython doesn’t have control anymore.

Cheers,

Sylvain

If the issue was GTK only - it is a known problem with IPython 0.10.1
for which the fix is waiting to be merged here:

https://github.com/ipython/ipython/issues/issue/237

but if you think the WX backend is also affected - it might just be
that you're not starting ipython with the -pylab flag to get the
threading to work without blocking. Can you try starting "ipython
-pylab -gthread" and "ipython -pylab -wthread" to see if that fixes
the issue? Make sure that you change the backend accordingly - and use
plt.get_backend() to ensure the appropriate one is being used.

···

On Fri, Dec 31, 2010 at 11:42 AM, Benjamin Root <ben.root@...1304...> wrote:

On Sun, Dec 19, 2010 at 3:34 AM, Sylvain Munaut <246tnt@...287...> wrote:

Hi,

I was wondering if you ever found a solution to this problem ?

I have the exact same issue with GTK (Agg or cairo) and WX backends
... I'm also under gentoo using ipython-0.10.1 and matplotlib-1.0.0
I don't have the warnings you have but same behavior, I have to call
show (if I don't a blank 'frozen' window is all that appears) but then
the ipython doesn't have control anymore.

Cheers,

Sylvain

It is very possible that this problem was fixed shortly after the 1.0.0 release. Another possibility is that ipython might be causing an issue where it is loading some older matplotlib codes before the rest of matplotlib 1.0.0 is loaded (I have seen this happen once).

You can test for this theory by seeing if you have the same problem when using the regular python shell. If not, then it is likely to be a problem with ipython. If you do have the same problem in regular python, then the problem is with matplotlib and you will need to build the latest from svn.

Ben Root

--
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7