On Jul 15, 2009, at 5:40 PM, tim awa wrote:
> In the class designer, when running the form, there is a debugger
> window. I have been looking at this window but there seems to be no
> activity there even when there is an error. To be able to see the
> error, I have to run the form/app at the console using python test.py.
Are you talking about the debugout window? That should normally not
be shown. It is designed to allow developers to include debugging code
that they can easily see without having a terminal window open.
> I found this at the wiki - http://dabodev.com/wiki/WinPDB. Any simpler
> alternative to WinPDB?
The normal Python debugger: pdb. You do have to work at the command
line, but it's way faster than running your app under WinPDB. I'm sure
that they've improved performance, but a couple of years ago when I
tried running WinPDB, it made the app so slow that I got frustrated
and switched back to pdb.
The other thing I do is add print statements to my code, run the app,
and then review the output in the terminal. This lets me get an idea
of what's going on so that I can quickly identify the cause of the
problem I'm having.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message:
http://leafe.com/archives/byMID/[email protected]
