From: Barry D. <bl...@ad...> - 2003-10-22 00:29:53
|
I installed the latest release 0.30 replacing 0.29, after uninstalling 0.29. I'm observing some difference in behavior between the two versions. Running some example code in 0.29, after closing the plot windows, the python.exe process quits normally. The same example using 0.30 hangs the process and I have to kill it by hand. This occurs both at the command line and from within my editor (normally I execute from the editor). I'm using Windows XP pro and UltraEdit. Any ideas? Do I need to change some set up from when I was using 0.29? Thanks. Barry --- John Hunter <jdh...@ac...> wrote: > > matplotlib is a 2D plotting package for python with > a matlab > compatible syntax and output tested under linux and > windows platforms. > > matplotlib-0.30 is available for download at > http://matplotlib.sourceforge.net, and has many new > features since the > last major release. > > Multiple outputs > > matplotlib now supports postscript and GD output, > as well as the > traditional GTK backend. The postscript backend > goes a long way > towards the goal of acheiving publication quality > output. The GD > backend allows you to use matplotlib even in > environments with no X > server, such as for a web application server > serving dynamic charts. > > Log scaling > > With the help of Andrew Straw, matplotlib now has > log axis > capabilities, with new commands semilogx, > semilogy and loglog > See > http://matplotlib.sourceforge.net/screenshots.html#log_shot > > Legends > > With the help of Charles R. Twardy, matplotlib now > has a matlab > compatible legend command. See > > http://matplotlib.sourceforge.net/screenshots.html#legend_demo > > Numerous bug fixes and minor additions > > DPI parameter allows multiple output resolutions > with correct > scaling > > Several bug fixes in GTK interactive mode using > examples/interactive2.py > > Multiple ways to specify colors, including matlab > compatible format > strings, RGB tuples, and html-style hex color > strings > > Rewrite of line class for much greater > compatibility with matlab > handle graphics commands and flexibility in > choosing line styles and > markers > > See > http://matplotlib.sourceforge.net/screenshots.html > for screenshots > and http://matplotlib.sourceforge.net/whats_new.html > for more detailed > information on what's new. > > John Hunter > _______________________________________________ > SciPy-user mailing list > Sci...@sc... > http://www.scipy.net/mailman/listinfo/scipy-user |
From: John H. <jdh...@ac...> - 2003-10-22 01:12:11
|
>>>>> "Barry" == Barry Drake <bl...@ad...> writes: Barry> I'm observing some difference in behavior between the two Barry> versions. Running some example code in 0.29, after closing Barry> the plot windows, the python.exe process quits normally. Barry> The same example using 0.30 hangs the process and I have to Barry> kill it by hand. This occurs both at the command line and Barry> from within my editor (normally I execute from the editor). Barry> Any ideas? Do I need to change some set up from when I was Barry> using 0.29? Yes. I made several changes to this part of matplotlib to iron out some interactive bugs, and a new one crept in; I didn't notice it in my tests. The quick fix is to add the following code to matplotlib/backends/backend_gtk.py at line 773 if GcfGTK.get_num_figwins()==0 and ShowOn().is_mainloop_on(): gtk.mainquit() This is in the GcfGTK.destroy function, so the entire function should read def destroy(num): if not GcfBase.has_fignum(num): return figwin = GcfGTK.figs[num] figwin.figure.drawable= None GcfBase.destroy(num) if GcfGTK.get_num_figwins()==0 and ShowOn().is_mainloop_on(): gtk.mainquit() destroy = staticmethod(destroy) This should restore the old functionality -- let me know if you see anymore strangeness. I'll check the change into CVS. [BTW, I posted the 0.30 announce to this mailing list this afternoon, but it didn't seem to make it. Hmmm.... Have I been moderated out of existence :-) ] Thanks for the bug report, John Hunter |
From: Barry D. <bl...@ad...> - 2003-10-22 05:00:26
|
Thanks John. That fixed the hanging process. Now a message is coming back "none active" from the function: def _get_active(self): if len(GcfBase._activeQue)==0: print 'None active' return None else: return self._activeQue[-1] in the _matlab_helpers.py file. I haven't traced it back further yet. Cheers. Barry --- John Hunter <jdh...@ac...> wrote: > >>>>> "Barry" == Barry Drake <bl...@ad...> > writes: > > Barry> I'm observing some difference in behavior > between the two > Barry> versions. Running some example code in > 0.29, after closing > Barry> the plot windows, the python.exe process > quits normally. > Barry> The same example using 0.30 hangs the > process and I have to > Barry> kill it by hand. This occurs both at the > command line and > Barry> from within my editor (normally I execute > from the editor). > > Barry> Any ideas? Do I need to change some set > up from when I was > Barry> using 0.29? > > Yes. I made several changes to this part of > matplotlib to iron out > some interactive bugs, and a new one crept in; I > didn't notice it in > my tests. The quick fix is to add the following > code to > matplotlib/backends/backend_gtk.py at line 773 > > if GcfGTK.get_num_figwins()==0 and > ShowOn().is_mainloop_on(): > gtk.mainquit() > > This is in the GcfGTK.destroy function, so the > entire function should > read > > def destroy(num): > if not GcfBase.has_fignum(num): return > figwin = GcfGTK.figs[num] > figwin.figure.drawable= None > GcfBase.destroy(num) > if GcfGTK.get_num_figwins()==0 and > ShowOn().is_mainloop_on(): > gtk.mainquit() > destroy = staticmethod(destroy) > > This should restore the old functionality -- let me > know if you see > anymore strangeness. I'll check the change into > CVS. > > [BTW, I posted the 0.30 announce to this mailing > list this afternoon, > but it didn't seem to make it. Hmmm.... Have I > been moderated out of > existence :-) ] > > Thanks for the bug report, > John Hunter |
From: John H. <jdh...@ac...> - 2003-10-22 07:16:26
|
>>>>> "Barry" == Barry Drake <bl...@ad...> writes: Barry> Thanks John. That fixed the hanging process. Now a Barry> message is coming back "none active" from the function: Barry> I haven't traced it back further yet. Just kill the line -- that was a diagnostic debug message that should have been removed before the release. Andrew Straw noted that a change I made in the axes module in 0.30 introduced a performance hit on his system. If you are experiencing similar problems, I also fixed this. plots should load approx twice as fast with the changes in CVS. JDH |