Re: [Gnumed-devel] review of possible checkin.

[Ian Haywood]

On Wed, Mar 16, 2005 at 09:15:35PM +1100, catmat wrote:
> Ian Haywood wrote:
> it's easier to use print statements, and then disable them with # after
> debugging the module :
Damned insolence ;-)

Of course its acceptable to use print in your own debugging,
but they should be removed before committing.
(completely, again,please don't clutter the code with pointless
commenting out)
> configuration level ,environment level or  the command line level ( is 
> it documented?).
Yes, in the module.

> One of the main reasons development is so slow is there is no step through
> debugger, or the technique for using one is not widely known,
Huh? python includes a step-through debugger (pdb), which is clearly
documented in the python docs.

I often insert:
import pdb
pdb.set_trace ()

before an interesting section of code, this fires up the debugger at
that point in the code.

> to an exception can be traced through line numbers in each module file."
This is the main reason: you have have one LogException in a wx event
handler,
 and it catches  everyting in code called by the handler.

> 
> Is anyone using a tool/editor that can link a log files  path  
> statements to  a
> editor to auto-open the module file concerned at the line number?
Yup, its called Emacs ;-))

Ian

pgpu4nCnPW39j.pgp
Description: PGP signature