Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New breakpoints can't be created in the IPython console #3476

Closed
lxkain opened this issue Sep 28, 2016 · 3 comments
Closed

New breakpoints can't be created in the IPython console #3476

lxkain opened this issue Sep 28, 2016 · 3 comments

Comments

@lxkain
Copy link

lxkain commented Sep 28, 2016

Description

What steps will reproduce the problem?

  1. create a breakpoint, start debugging, and continue to the next breakpoint
  2. during the interactive ipdb sessions, add a second breakpoint further down the road
  3. continue execution

What is the expected output? What do you see instead?
I expect the debugger to pause at the second breakpoint. Instead it ignores it (i.e. all breakpoints need to be specified before debugging)

Please provide any additional information below

Version and main components

  • Spyder Version: 3.0.0
  • Python Version: 3.4.5
  • Qt Versions: 4.8.7, PyQt4 (API v2) 4.11.4 on Darwin

Dependencies

pyflakes >=0.6.0 :  1.3.0 (OK)
pep8 >=0.6       :  1.7.0 (OK)
pygments >=2.0   :  2.1.3 (OK)
qtconsole >=4.2.0:  4.2.1 (OK)
nbconvert >=4.0  :  4.2.0 (OK)
pandas >=0.13.1  :  0.18.1 (OK)
numpy >=1.7      :  1.11.1 (OK)
sphinx >=0.6.6   :  1.4.6 (OK)
rope >=0.9.4     :  0.9.4-1 (OK)
jedi >=0.8.1     :  0.9.0 (OK)
psutil >=0.3     :  4.3.1 (OK)
matplotlib >=1.0 :  1.5.1 (OK)
sympy >=0.7.3    :  1.0 (OK)
pylint >=0.25    :  1.6.4 (OK)

@ccordoba12 ccordoba12 added this to the v3.0.1 milestone Sep 29, 2016
@ccordoba12 ccordoba12 changed the title new breakpoints cannot be created during debugging New breakpoints can't be created in the IPython console Sep 29, 2016
@ccordoba12
Copy link
Member

Thanks for reporting. I'm aware of this problem but I didn't have time to fix it for 3.0.

@lxkain
Copy link
Author

lxkain commented Sep 29, 2016

Sure, I understand. My plethora of bug reports simply shows my excitement for the new version :)

On Sep 29, 2016, at 00:25, Carlos Cordoba notifications@github.com wrote:

Thanks for reporting. I'm aware of this problem but I didn't have time to fix it for 3.0.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@goanpeca goanpeca modified the milestones: v3.0.1, v3.1 Oct 5, 2016
@ccordoba12 ccordoba12 modified the milestones: v3.0.1, v3.1 Oct 6, 2016
@ccordoba12
Copy link
Member

@rlaverde, please solve this one this week. Take a look at PR #3561 to understand how to proceed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants