From: Collin D. <dcd...@gm...> - 2010-11-18 00:55:28
|
Either I updated something that changed Matplotlib's behavior or I am missing something, but when I make a plot in ipython, control is not returning to the prompt - I can't do anything until I close the plot. Here is exactly what I am doing: ipython --pylab x=arange(10) y=x**2 figure() plot(x,y) show() Also, I am not sure if that is right. In the past I remember just being able to type plot() and the figure came up and control went back to ipython to continue. But I could be wrong. Then, if I want to do anything else, I have to close the window. The backend I am using is WXAgg. I also noticed that if I use the GTKAgg backend, control does not return to the prompt even after closing the plot. I have to hit ctl-c to get the prompt back. I have tried this both with ion() and ioff(). I don't ever remember having to close the plot or hit control-c to keep working. I googled and did not really see anything relevant. Could anyone tell me what I am missing or what I need to do so that I can plot in ipython, leave the plot up, and then continue working? I have matplotlib 1.0.0 and ipython 0.10.1 Thanks for any help! |
From: Sylvain M. <24...@gm...> - 2010-12-19 09:34:42
|
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 |
From: Benjamin R. <ben...@ou...> - 2010-12-31 19:43:08
|
On Sun, Dec 19, 2010 at 3:34 AM, Sylvain Munaut <24...@gm...> 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 |
From: Paul I. <piv...@gm...> - 2011-01-01 00:20:03
|
On Fri, Dec 31, 2010 at 11:42 AM, Benjamin Root <ben...@ou...> wrote: > > On Sun, Dec 19, 2010 at 3:34 AM, Sylvain Munaut <24...@gm...> 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 > 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. -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 |
From: Benjamin R. <ben...@ou...> - 2010-11-18 01:01:22
|
On Wed, Nov 17, 2010 at 6:54 PM, Collin Day <dcd...@gm...> wrote: > Either I updated something that changed Matplotlib's behavior or I am > missing something, but when I make a plot in ipython, control is not > returning to the prompt - I can't do anything until I close the plot. > Here is exactly what I am doing: > > ipython --pylab > > x=arange(10) > y=x**2 > > figure() > plot(x,y) > show() > > Also, I am not sure if that is right. In the past I remember just being > able to type plot() and the figure came up and control went back to > ipython to continue. But I could be wrong. > > Then, if I want to do anything else, I have to close the window. The > backend I am using is WXAgg. I also noticed that if I use the GTKAgg > backend, control does not return to the prompt even after closing the > plot. I have to hit ctl-c to get the prompt back. I have tried this > both with ion() and ioff(). > > I don't ever remember having to close the plot or hit control-c to keep > working. I googled and did not really see anything relevant. Could > anyone tell me what I am missing or what I need to do so that I can > plot in ipython, leave the plot up, and then continue working? > > I have matplotlib 1.0.0 and ipython 0.10.1 > > Thanks for any help! > > Most likely, you were used to interactive mode being on. A new installation of matplotlib might have over-written your matplotlibrc file, resetting the option to False. Find your matplotlibrc file and change interactive to True to get the behavior you want. I hope that helps! Ben Root |
From: Collin D. <dcd...@gm...> - 2010-11-18 01:39:10
|
On Wed, 17 Nov 2010 19:00:54 -0600 Benjamin Root <ben...@ou...> wrote: Another data point - I tried Qt4Agg - it also works interactively - ie it goes back to the ipython cmd line. I also noticed when I start ipython --pylab, the following error messages occur: ** Message: pygobject_register_sinkfunc is deprecated (GtkWindow) ** Message: pygobject_register_sinkfunc is deprecated (GtkInvisible) ** Message: pygobject_register_sinkfunc is deprecated (GtkObject) -C > On Wed, Nov 17, 2010 at 6:54 PM, Collin Day <dcd...@gm...> > wrote: > > > Either I updated something that changed Matplotlib's behavior or I > > am missing something, but when I make a plot in ipython, control is > > not returning to the prompt - I can't do anything until I close the > > plot. Here is exactly what I am doing: > > > > ipython --pylab > > > > x=arange(10) > > y=x**2 > > > > figure() > > plot(x,y) > > show() > > > > Also, I am not sure if that is right. In the past I remember just > > being able to type plot() and the figure came up and control went > > back to ipython to continue. But I could be wrong. > > > > Then, if I want to do anything else, I have to close the window. > > The backend I am using is WXAgg. I also noticed that if I use the > > GTKAgg backend, control does not return to the prompt even after > > closing the plot. I have to hit ctl-c to get the prompt back. I > > have tried this both with ion() and ioff(). > > > > I don't ever remember having to close the plot or hit control-c to > > keep working. I googled and did not really see anything relevant. > > Could anyone tell me what I am missing or what I need to do so that > > I can plot in ipython, leave the plot up, and then continue working? > > > > I have matplotlib 1.0.0 and ipython 0.10.1 > > > > Thanks for any help! > > > > > Most likely, you were used to interactive mode being on. A new > installation of matplotlib might have over-written your matplotlibrc > file, resetting the option to False. Find your matplotlibrc file and > change interactive to True to get the behavior you want. > > I hope that helps! > > Ben Root |
From: Benjamin R. <ben...@ou...> - 2010-11-18 01:47:01
|
On Wed, Nov 17, 2010 at 7:38 PM, Collin Day <dcd...@gm...> wrote: > On Wed, 17 Nov 2010 19:00:54 -0600 > Benjamin Root <ben...@ou...> wrote: > > Another data point - > > I tried Qt4Agg - it also works interactively - ie it goes back to the > ipython cmd line. I also noticed when I start ipython --pylab, the > following error messages occur: > > ** Message: pygobject_register_sinkfunc is deprecated (GtkWindow) > ** Message: pygobject_register_sinkfunc is deprecated (GtkInvisible) > ** Message: pygobject_register_sinkfunc is deprecated (GtkObject) > > Interesting. It is possible that the gtk backend might have been compiled against gtk development libraries that do not match your current gtk library. What have you updated recently, and how did you do it? Ben Root |
From: Collin D. <dcd...@gm...> - 2010-11-18 01:58:58
|
Well, I am a Gentoo user, so I was doing the usual emerge -uavDN world which updates everything, so I don't know what exactly has changed. What I can tell you is that I have gtk 2.20.1 and wxGtk 2.8.11. I could try updating again (I update about every 1-2 weeks to keep current and avoid issues that can arise when you update from older stuff). Also, I can just use TkAgg as it works. If it is something you are interested in, I don't mind trying some debug stuff if you let me know what you need to debug. Otherwise - tkAgg appears to be the way to go:) At least someone knows there is a potential problem. How about I try a system update and let you know if I still see problems? -C On Wed, 17 Nov 2010 19:46:34 -0600 Benjamin Root <ben...@ou...> wrote: > On Wed, Nov 17, 2010 at 7:38 PM, Collin Day <dcd...@gm...> > wrote: > > > On Wed, 17 Nov 2010 19:00:54 -0600 > > Benjamin Root <ben...@ou...> wrote: > > > > Another data point - > > > > I tried Qt4Agg - it also works interactively - ie it goes back to > > the ipython cmd line. I also noticed when I start ipython --pylab, > > the following error messages occur: > > > > ** Message: pygobject_register_sinkfunc is deprecated (GtkWindow) > > ** Message: pygobject_register_sinkfunc is deprecated (GtkInvisible) > > ** Message: pygobject_register_sinkfunc is deprecated (GtkObject) > > > > > Interesting. It is possible that the gtk backend might have been > compiled against gtk development libraries that do not match your > current gtk library. What have you updated recently, and how did you > do it? > > Ben Root |
From: Collin D. <dcd...@gm...> - 2010-11-19 00:58:34
|
So I tried updating and rebuilding Matplotlib - no luck - something (at least on my system) is goofy with the GTK(Agg),WX(Agg), and Fltk(Agg) backends. But the TkAgg backend works great. So I will stick with that, but if anyone else sees this problem and it becomes an issue, I'd be happy to help debug it in any way I can. -C On Wed, 17 Nov 2010 19:46:34 -0600 Benjamin Root <ben...@ou...> wrote: > On Wed, Nov 17, 2010 at 7:38 PM, Collin Day <dcd...@gm...> > wrote: > > > On Wed, 17 Nov 2010 19:00:54 -0600 > > Benjamin Root <ben...@ou...> wrote: > > > > Another data point - > > > > I tried Qt4Agg - it also works interactively - ie it goes back to > > the ipython cmd line. I also noticed when I start ipython --pylab, > > the following error messages occur: > > > > ** Message: pygobject_register_sinkfunc is deprecated (GtkWindow) > > ** Message: pygobject_register_sinkfunc is deprecated (GtkInvisible) > > ** Message: pygobject_register_sinkfunc is deprecated (GtkObject) > > > > > Interesting. It is possible that the gtk backend might have been > compiled against gtk development libraries that do not match your > current gtk library. What have you updated recently, and how did you > do it? > > Ben Root |