[Python-Dev] seeing off SET_LINENO

Michael Hudson mwh@python.net
31 Jul 2002 09:22:22 +0100

"Mark Hammond" <mhammond@skippinet.com.au> writes:

> > Michael Hudson <mwh@python.net>:
> >
> > > My patch means the debugger doesn't stop
> > > on the "def f():" line -- unsurprisingly, given that no execution ever
> > > takes place on that line.
> [Greg]
> > If there is no code there, there shouldn't be any
> > need to stop there, should there?
> [Barry in a different message]
> > I can't decide whether it would be good to stop on the def or not.
> > Not doing so makes pdb act more like gdb, which also only stops on the
> > first executable line, so maybe that's a good thing.
> IMO, the Python debugger "interface" should include function entry.  

There goes the time machine: it does.  I just think everyone ignores
'call' messages because they're a bit redundant today (because of the
matter under discussion).

> The debugger UI (in this case pdb, but any other debugger) may
> choose not to break there, but the debugger itself may be able to
> implement some useful things by having the hook.

bdb.Bdb.user_call(), I believe.


  One of the great skills in using any language is knowing what not
  to use, what not to say.  ... There's that simplicity thing again.
                                                       -- Ron Jeffries