This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: IPython 5.3.0 debug mode breakpoint issue
Type: crash Stage: resolved
Components: Versions: Python 2.7
Status: closed Resolution: third party
Dependencies: Superseder:
Assigned To: Nosy List: Taylor Newton, berker.peksag
Priority: normal Keywords:

Created on 2017-05-15 14:43 by Taylor Newton, last changed 2022-04-11 14:58 by admin. This issue is now closed.

File name Uploaded Description Edit
ipython_error Taylor Newton, 2017-05-15 14:43 ipython error example
Messages (2)
msg293712 - (view) Author: Taylor Newton (Taylor Newton) Date: 2017-05-15 14:43
Hi Python Team,

I recently upgraded Python to version 2.7.8 (from 2.6.6) and IPython to version 5.3.0.  I noticed that when using the magic command (%run -d) in IPython, subsequent runs of a program seem to fail with a "KeyError", apparently due to the debugger's failure to clear breakpoints from previous runs of the program.

I attached a sample of output from one such failed run, where a breakpoint that had been set at line 56 in a previous call caused the program to crash, though in the current call, only one breakpoint at line 70 is requested.  

For the time being, I've downgraded to IPython version 4.2.0, which seems to work as expected.

msg293719 - (view) Author: Berker Peksag (berker.peksag) * (Python committer) Date: 2017-05-15 16:09
Thanks for the report, but IPython is not part of the Python standard library. Since downgrading IPython to 4.2.0 solved your problem, I'd suggest to report this to IPython developers.
Date User Action Args
2022-04-11 14:58:46adminsetgithub: 74555
2017-05-15 16:09:45berker.peksagsetstatus: open -> closed

nosy: + berker.peksag
messages: + msg293719

resolution: third party
stage: resolved
2017-05-15 14:43:43Taylor Newtoncreate