Why is it that if I have a syntax error in a wxpython program that it
doesn't show me where the problem is? I get this print out about
memory
leaks and whatnot, when the real problem is that I just had a syntax
error.
Is it possible to see normal python tracebacks?
It depends on where the error occurs. If it is in a callback or event
handler then PyErr_Print() is called. It is supposed to print the
full
traceback but I've also seen that in some situations it only prints
the
actual error without the traceback...
I've been seeing this as well. I'm editing my code in PythonWin (on
Win98) and then running it from a command prompt. Every time I have an
uncaught exception (including syntax errors), I get a long listing of
memory leaks. I'm presuming that the leaks are happening only because
there is no proper shutdown, as nothing is printed when I exit
normally. I'm also presuming that there *is* a traceback printed, but
that it scrolls out of sight before I can see it. My workaround has been
that, if I get an exception, I try running again *within*
PythonWin--then, I see the traceback in PW's interactive window, but no
memory leak report. I try to avoid running working wxPython code within
PW, though, as running GUI code from within a GUI tool frequently has
issues...
As a minor side note, I've been having some confusion trying to figure
out from the docs and the wxpywiki how to do some detailed arrangement
with wxSizers. The current docs are not terribly clear just how all the
different options interact, and the example code is very basic, so it
doesn't really help. If anyone happens to be working on docs, this is
an area that could use some work... Yeah, I know, this is open source,
I should do it myself. 
Hopefully once I get everything cleared up
in my mind, I'll have time to write up something to explain it more
clearly, and submit it to the wiki...
Jeff Shannon
Technician/Programmer
Credit International