Ok, I see that you both use print statements as a debugging tool. It's
much the same way I do it (with no compile time this is ok), but from
time to time you need a good debugger, and it will be a very big
turn-off for people if dabo is impossible to debug. Why are debuggers
crashing etc. with dabo? I have now tries several different debuggers,
and none work with dabo.
-Simen
-----Original Message-----
From: dabo-users-bounces At leafe .D.OT com [mailto:dabo-users-bounces@leafe.com]
On Behalf Of Ed Leafe
Sent: 30. juni 2006 15:01
To: Dabo Users list
Subject: Re: [dabo-users] Developing and debugging dabo applications
On Jun 30, 2006, at 7:44 AM, Simen Haugen wrote:
> It's a real pain in the ass to debug without a debugger. What IDE and
> debuggers to you use with dabo (and python development in general)?
I used Winpdb a while back, and while I never ran into the
problems
with locals that you seem to have, I just found it way to slow to
start up, and the fact that you can't put a breakpoint in your code
makes it almost useless to me, since that means I have no simple way
of skipping over the stuff that I'm not working on.
Like Paul, I use lots of print statements in my code and read
the
output in the terminal window to find out where things are not
working as expected. When I need to step through code, I can just add
'dabo.trace()' to invoke the pdb debugger.
With the exception of the tricks used to get .cdxml code to
execute
as instance methods of the objects, there is nothing that is not
straight wxPython in any of our UI code, and nothing that is not
plain vanilla Python in the rest. There is no outside magic
happening; it's just Python.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
©2006 Simen Haugen |
