Skip to content

pressin F5 does not trigger debugging the script / running the code / manually run code does not wipe the debug console #271

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

Closed
Balky79 opened this issue Nov 21, 2017 · 1 comment
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@Balky79
Copy link

Balky79 commented Nov 21, 2017

Environment data

VS Code version: 1.18.1
Python Extension version: 0.80.0
Python Version: 3.4.2
OS and version: Windows 10

Actual behaviour

F5 or Control F5 does not react when I want to start debugging/running my python script
Clicking ">Python" in the tray, then Debug in Python on top of the screen works, but it does not clean "Debug Console" window anymore.

Expected behaviour

The script should run as it was running in Vscode 1.17, when keys are used.
Debug screen should be cleared on each run, or configurable.

Steps to reproduce:

open python script in vscode.
Press "F5" to debug it
Press "Ctrl F5" to run it

Logs

Output from Python output panel

Output from Console window (Help->Developer Tools menu)

No logs whatsoever, it just does nothing.
This is a copy of: microsoft/vscode#38371

@DonJayamanne
Copy link

Duplicate of #25

@DonJayamanne DonJayamanne marked this as a duplicate of #25 Nov 21, 2017
@DonJayamanne DonJayamanne added this to the December 2017 milestone Nov 21, 2017
@DonJayamanne DonJayamanne added closed-duplicate area-debugging bug Issue identified by VS Code Team member as probable bug labels Nov 21, 2017
@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 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

No branches or pull requests

2 participants