Author ltaylor934
Recipients ltaylor934
Date 2012-02-24.01:35:25
SpamBayes Score 6.10443e-11
Marked as misclassified No
Message-id <1330047327.02.0.291761854329.issue14105@psf.upfronthosting.co.za>
In-reply-to
Content
My environment is Windows XP, using IDLE and Python 2.7 distribution.

Open an IDLE Python shell. Open the file with three lines in it, 1,2 and 3.

In IDLE, Set Breakpoint on Line 2.

In Shell, set Debug.

In IDLE, select run. 

In the Debug window, click Go.

Run stops at line 2, displayed in Debug. Click Quit.

Edit the file, inserting a line 0, like: print "this is line 0". Save the file

Run again, Go in Debug. 

The breakpoint has disappeared and the debugger does not stop on line 2 (now the third line). It doesn't stop anywhere.

Delete line 0, and set breakpoint on line 2 again. At the end of the file, insert a line 4, such as: print "this is line 4".

Run again, Go in Debug.

The breakpoint is preserved, and the debugger stops at line 2.

This is inconsistent behavior. I expect that a breakpoint will not disappear, and that it will always point to the same line, moving down when the line moves down. The breakpoint should move up if the line it refers to moves up.
History
Date User Action Args
2012-02-24 01:35:27ltaylor934setrecipients: + ltaylor934
2012-02-24 01:35:27ltaylor934setmessageid: <1330047327.02.0.291761854329.issue14105@psf.upfronthosting.co.za>
2012-02-24 01:35:26ltaylor934linkissue14105 messages
2012-02-24 01:35:25ltaylor934create