Unexpected behavior in PythonWin Debugger

[Mark Hammond]

There is a strange thing when debugging the bottom( ie, only!) stack frame -
if you put the code into a function, it should step fine (as the function is
no longer at the bottom.  I intend giving the debugger a good going over
fairly soon...

Mark.

cmedcoff at my-dejanews.com wrote in message <7gvrvl$6dd$1 at nnrp1.deja.com>...
>Consider the following.
>
>import sys
>for x in sys.argv:
> print x
>
>Debug the following script with the arguments "foo on you". When you press
>the "step" button on the line "print x" it steps into the function.  When
you