matplotlib-devel Mailing List for matplotlib

Hi John,
 My apologies for apparently missing your earlier response.
Interesting enough, last night when i was looking around in the 
backend_wx.py code for what might be causing those debug messages,
i thought that line: 
> wxInitAllImageHandlers() 
in conjunction the "Adding duplicate image handler" looked
suspect. I briefly thought about commenting it out...but i
figured that would probably break the tool bar icons etc. 
As you suggested, i tried commenting that line out, and sure
enough: no debug messages...and my app that does some plotting 
appears to work fine.
Thanks a lot!!
Glad my report led you to a problem you were looking for.
Jim
On 2004年4月17日, John Hunter wrote:
> 
> Hi Jim,
> 
> I responded to this earlier today on matplotlib-users. Here is a copy
> of my post. I'm very interested in getting some feedback if you try
> the suggestion below.
> 
> JDH
> 
> 
> >>>>> "Jim" == Jim Benson <jb...@se...> writes:
> 
> Jim> Hi,
> 
> Jim> I seem to be seeing some extra debug output. I have been
> Jim> using the wx background and the embedding_in_wx.py example as
> Jim> a template for how to make matplotlib plots in an app i'm
> Jim> writing. This part works great!! I am however seeing what
> Jim> appears to be a debug flag left on somewhere?
> 
> No, this is in the wx code. I traced it to the line
> 
> wxInitAllImageHandlers()
> 
> Miraculously, I commented this out, got rid of the annoying messages,
> and fixed the wx exception swallowing bug! Jeremy and I have been
> killing ourselves for about 6 months trying to figure out why backend
> wx was swallowing our exceptions, and I can't really convey how happy
> I am to have found this. We have tried all manner of hacks, google
> searches and plantive pleas to get our exceptions back to no avail.
> It made debugging wx virtually impossible.
> 
> Please test this change on your system. win32 users, I would also be
> much obliged if you could try commenting this out on your system to
> see if you lose functionality. On my linux box, the figures came up
> as expected, I was able to print to jpg and png, so all looks well.
> 
> Note, wxagg is in CVS if you need some of the agg features that native
> wx drawing does not provide. But it looks like all systems are go for
> a release next week so you may as well wait.
> 
> JDH
> 
> 
-- 
Dr. James A. Benson
United States Naval Observatory
Navy Prototype Optical Interferometer
Flagstaff, AZ 86001
Email: jb...@no...
 jb...@se...
Voice: 928-773-4868/928-779-5132
Fax: 928-779-9568

Hi Jim,
I responded to this earlier today on matplotlib-users. Here is a copy
of my post. I'm very interested in getting some feedback if you try
the suggestion below.
JDH
>>>>> "Jim" == Jim Benson <jb...@se...> writes:
 Jim> Hi,
 Jim> I seem to be seeing some extra debug output. I have been
 Jim> using the wx background and the embedding_in_wx.py example as
 Jim> a template for how to make matplotlib plots in an app i'm
 Jim> writing. This part works great!! I am however seeing what
 Jim> appears to be a debug flag left on somewhere?
No, this is in the wx code. I traced it to the line
 wxInitAllImageHandlers()
Miraculously, I commented this out, got rid of the annoying messages,
and fixed the wx exception swallowing bug! Jeremy and I have been
killing ourselves for about 6 months trying to figure out why backend
wx was swallowing our exceptions, and I can't really convey how happy
I am to have found this. We have tried all manner of hacks, google
searches and plantive pleas to get our exceptions back to no avail.
It made debugging wx virtually impossible.
Please test this change on your system. win32 users, I would also be
much obliged if you could try commenting this out on your system to
see if you lose functionality. On my linux box, the figures came up
as expected, I was able to print to jpg and png, so all looks well.
Note, wxagg is in CVS if you need some of the agg features that native
wx drawing does not provide. But it looks like all systems are go for
a release next week so you may as well wait.
JDH

Hi,
 After i posted a version of this question on the 
matplotlib-users list i decided it would probably be better
to post it on the devel list. Here is the problem, if i include 
any one of the following three lines: 
from matplotlib.backends.backend_wx import FigureCanvasWx
#from matplotlib.backends.backend_wx import Toolbar
#from matplotlib.backends.backend_wx import FigureManager
 
(here only the first one is uncommented...same result if i
use either of the other two) in a file (test.py) and then type: 
python test.py
i get:
floyd:/home/jbenson/python>python test.py
[Debug] 15:17:10: Adding duplicate image handler for 'PNG file'
[Debug] 15:17:10: Adding duplicate image handler for 'JPEG file'
[Debug] 15:17:10: Adding duplicate image handler for 'TIFF file'
[Debug] 15:17:10: Adding duplicate image handler for 'GIF file'
[Debug] 15:17:10: Adding duplicate image handler for 'PNM file'
[Debug] 15:17:10: Adding duplicate image handler for 'PCX file'
[Debug] 15:17:10: Adding duplicate image handler for 'XPM file'
[Debug] 15:17:10: Adding duplicate image handler for 'Windows icon file'
[Debug] 15:17:10: Adding duplicate image handler for 'Windows cursor file'
[Debug] 15:17:10: Adding duplicate image handler for 'Windows animated 
cursor file'
floyd:/home/jbenson/python>
If i try the same line from a python prompt line:
floyd:/home/jbenson>python
Python 2.3.3 (#1, Dec 21 2003, 15:13:18)
[GCC 3.3.1] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from matplotlib.backends.backend_wx import FigureCanvasWx
>>>
...no extra debug lines. I'm using matplotlib-0.52. Does anyone recognize
where those [Debug] statements are coming from, and how i could
get them to not show up? 
Thanks,
Jim

>>>>> "Andrew" == Andrew Straw <str...@as...> writes:
 >> The stumper for me is that I have been unable to build
 >> scipy/numpy for the python that is bundled with os x - has
 >> anyone been successful with this? 
I have. Check the scipy mailing list archives (search for OS X).
There are several useful threads. Also, use scipy CVS, as a number of
darwin specific fixes have been added.
JDH

>>>>> "Kenneth" == Kenneth McDonald <kmm...@wi...> writes:
 Kenneth> I believe this is the right list, since the question
 Kenneth> deals with compiling, rather than using, matplotlib.
 Kenneth> Hope that's OK.
Fine by me...
 Kenneth> I just dl'ed, and after setting the TkAgg flag to 1 in
 Kenneth> setup.py, did a python setup.py install. (Note that I had
 Kenneth> done a previous install without the TkAgg flag set.) On
 Kenneth> my system, this is producing a bunch of errors related to
 Kenneth> the Tk headers:
Generally only the first error message from the compiler is
informative. Subsequent ones often indicate a downstream component
that failed after the first failed. In your case, the 1st error is
 In file included from src/_tkagg.cpp:18:
 /Library/Frameworks/Tk.framework/Headers/tk.h:96:29: X11/Xlib.h: No
 such file or directory
So it looks to me that either you haven't installed X11 (which is the
default config on OS X) or it's not in your include path. If you
haven't installed X11 for OS X, see
http://www.apple.com/macosx/features/x11.
After you get past this hurdle, you might encounter another road block
or two, especially if you are a fink user. In that case, you may want
to edit setupext.py and replace the dictionary entry
 'darwin' : '/usr/local',
with
 'darwin' : '/sw',
and check out this post
http://sourceforge.net/mailarchive/message.php?msg_id=7777103
Good luck!
JDH

I believe this is the right list, since the question deals with
compiling, rather than using, matplotlib. Hope that's OK.
I just dl'ed, and after setting the TkAgg flag to 1 in setup.py,
did a python setup.py install. (Note that I had done
a previous install without the TkAgg flag set.) On my system,
this is producing a bunch of errors related to the Tk headers:
...
running build_ext
building 'matplotlib.backends._tkagg' extension
creating build/temp.darwin-7.3.0-Power_Macintosh-2.3
creating build/temp.darwin-7.3.0-Power_Macintosh-2.3/src
gcc -fno-strict-aliasing -Wno-long-double -no-cpp-precomp 
-mno-fused-madd -fno-common -dynamic -DNDEBUG -g -O3 -Wall 
-Wstrict-prototypes -I/usr/local/include -I/usr/local/include/freetype2 
-Isrc -Iagg2/include 
-I/System/Library/Frameworks/Python.framework/Versions/2.3/include/ 
python2.3 -c src/_tkagg.cpp -o 
build/temp.darwin-7.3.0-Power_Macintosh-2.3/src/_tkagg.o
In file included from src/_tkagg.cpp:18:
/Library/Frameworks/Tk.framework/Headers/tk.h:96:29: X11/Xlib.h: No 
such file or directory
In file included from src/_tkagg.cpp:18:
/Library/Frameworks/Tk.framework/Headers/tk.h:572: error: 
`Tk_ClassCreateProc'
 was not declared in this scope
/Library/Frameworks/Tk.framework/Headers/tk.h:573: error: type specifier
 omitted for parameter `Window'
/Library/Frameworks/Tk.framework/Headers/tk.h:573: error: parse error 
before `,
 ' token
/Library/Frameworks/Tk.framework/Headers/tk.h:573: error: typedef 
`Window' is
 initialized (use __typeof__ instead)
/Library/Frameworks/Tk.framework/Headers/tk.h:576: error: type specifier
 omitted for parameter `XEvent'
...
and so on, for a very long time.
I have done some messing around with Tk--I'm currently running 
AquaTcl/Tk, not the
X11 version--but don't have a good handle on how to deal with the 
above. Any
ideas? I'd really like to start using matplotlib!
Thanks,
Ken McDonald