[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Roundup Robot added the comment: New changeset 71fe5e336d5b by Terry Jan Reedy in branch '2.7': Issue #14105: Change comment to reflect fix. Patch by Saimadhav Heblikar. https://hg.python.org/cpython/rev/71fe5e336d5b New changeset f33b4770a078 by Terry Jan Reedy in branch '3.4': Issue #14105: C

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Saimadhav Heblikar added the comment: While working on issue22083, I noticed a few redundant comments. This patch removes them. -- keywords: +patch Added file: http://bugs.python.org/file36349/remove-pyshell-comment.diff ___ Python tracker

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Terry J. Reedy added the comment: Forgot to mention: after inserting \n, the breakpoint tag can be cleared from either line independently. Tagging complete lines makes this easy. If a line is split into three and the middle line untagged, then the first and third are left separately tagged. -

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Terry J. Reedy added the comment: On 8/9/2014 10:13 AM, Saimadhav Heblikar wrote: > > Saimadhav Heblikar added the comment: > > Not sure if this consequence of the commit is intended behavior, It is. > In any file, set a breakpoint on any line. Pressing key > anywhere after the first character

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Saimadhav Heblikar added the comment: Not sure if this consequence of the commit is intended behavior, but still placing it here. In any file, set a breakpoint on any line. Pressing key anywhere after the first character, will create a new breakpoint in the next line. These lines will also

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Terry J. Reedy added the comment: I moved the BREAK tag configuration to PyShell.PyShellEditorWindow, which adds breakpoint support by subclassing EditorWindow. I wrapped the code in a function so we can also unconfig BREAK text colorizing. This might be desired when colored line numbers indic

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Roundup Robot added the comment: New changeset 76ca8569a04c by Terry Jan Reedy in branch '2.7': Issue #14105: Stop removing breakpoints from Idle editors. http://hg.python.org/cpython/rev/76ca8569a04c New changeset d775fa9a9767 by Terry Jan Reedy in branch '3.4': Issue #14105: Stop removing brea

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Changes by Mark Lawrence : -- versions: +Python 3.5 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Changes by Terry J. Reedy : -- versions: +Python 3.4 -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Roger Serwy added the comment: The ColorDelegator is responsible for providing the coloring for the BREAK tag which is used to mark breakpoints. When recoloring, the BREAK tag may be removed (find self.tag_remove in recolorize_main). This is precisely why the breakpoints disappear. On 2.7, y

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

Changes by Terry J. Reedy : -- nosy: +terry.reedy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue14105] Breakpoints in debug lost if line is inserted; IDLE

New submission from Larry A. Taylor : 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.