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

"assert False" hangs with "Breakpoints" on for "All Exceptions" #1194

Closed
bersbersbers opened this issue Mar 26, 2018 · 2 comments · Fixed by #1599
Closed

"assert False" hangs with "Breakpoints" on for "All Exceptions" #1194

bersbersbers opened this issue Mar 26, 2018 · 2 comments · Fixed by #1599
Assignees
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@bersbersbers
Copy link

"assert False" hangs with "Breakpoints" on for "All Exceptions" - see snapshot:

image

Environment data

  • VS Code version: 1.21.1
  • Extension version (available under the Extensions sidebar): Python, macros
  • OS and version: Microsoft Windows [Version 10.0.16299.309]
  • Python version (& distribution if applicable, e.g. Anaconda): Python 3.6.4
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): None that I know of, but I am new to Python. Help me find out :)
  • Relevant/affected Python packages and their versions: none, I think

Actual behavior

Debugging never finishes

Expected behavior

Traceback (most recent call last):
  File "c:\Temp\AssertFalse.py", line 1, in <module>
    assert(False)
AssertionError

Steps to reproduce:

  1. Activate "Breakpoints: All Exceptions"
  2. Debug Code including assert (False)

Logs

Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

(nothing)

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

(nothing)
@brettcannon brettcannon added bug Issue identified by VS Code Team member as probable bug needs verification area-debugging labels Mar 26, 2018
@brettcannon
Copy link
Member

I can confirm this, although the experimental debugger is what we are working on but doesn't support those exception options yet.

@bersbersbers
Copy link
Author

Just adding that this happens not only with assert False, but also with assert False "". It does not happen with assert False "Hello world.", so the empty or non-existent string may be an issue.

@DonJayamanne DonJayamanne self-assigned this May 3, 2018
@DonJayamanne DonJayamanne added this to the May 2018 milestone May 3, 2018
DonJayamanne added a commit that referenced this issue May 7, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants