[Python-Dev] seeing off SET_LINENO

[Mark Hammond]

> 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.  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.

Mark.