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

Python: 'Start without debugging shortcut’ has a problem. #35

Closed
weinand opened this issue Nov 10, 2017 · 11 comments
Closed

Python: 'Start without debugging shortcut’ has a problem. #35

weinand opened this issue Nov 10, 2017 · 11 comments
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@weinand
Copy link

weinand commented Nov 10, 2017

From @weqopy on November 9, 2017 13:32

  • VSCode Version: 1.18
  • OS Version: macOS High Sierra 10.13.1

Steps to Reproduce:

  1. Set "stopOnEntry" to false in launch.json
  2. run python file with debug, it returns result fast, run it again, the result disappears and returns again
  3. but when use 'ctrl + F5' to run it without debug, it's not end in fact as these two screenshots show, and there will be no response when I try to run it again with or without debug.

2017-11-09 21 22 40

2017-11-09 21 22 49

4. click the debug in status bar and runs it, VS Code returns this:

2017-11-09 21 30 51

5. At last, I have to use cmd+Q to quit Code and restart it

Reproduces without extensions: Yes/No

Copied from original issue: microsoft/vscode#37946

@weinand
Copy link
Author

weinand commented Nov 10, 2017

From @greenlong on November 10, 2017 5:33

I have same problem.

VSCode Version: 1.18
OS Version: Windows 10

@nbara
Copy link

nbara commented Nov 13, 2017

I've been having the same problem for a few days now. Since the last Python extension update to be exact.

@federicobarera
Copy link

federicobarera commented Nov 14, 2017

In my case when I launch any python debug configuration with the CTRL + F5 combination the code executes but the debugger stays attached. Not exiting, prevents any other start debug configuration from starting. Only solution is to close and re-open vscode.

V 1.18.0 x64
Win 10

@DonJayamanne DonJayamanne added the bug Issue identified by VS Code Team member as probable bug label Nov 14, 2017
@brettcannon
Copy link
Member

Closing this as a duplicate of #25

@DonJayamanne DonJayamanne added this to the December 2017 milestone Nov 17, 2017
DonJayamanne added a commit that referenced this issue Nov 22, 2017
#249)

- Fixes #25, #32, #35, #235, #242 (unable to run without debugging using CTRL+F5)   
- Fixes #191, #158, #24, #136  (error message displayed when debugged code terminates)  
- Fixes #157 (debugger crashes when python program does not launch)
- Fixes #114, #149, #250 (use vscode infrastructure to launch debugger in integrated and external terminals)  
- Fixes #239 Remove prompt added to pause terminal upon program completion
@jsonMartin
Copy link

I'm still having this issue

@brettcannon
Copy link
Member

@jsonMartin did you test w/ the in-development version of the extension which has the fix? Otherwise you should receive the fix in the next public release which is scheduled for mid-December.

@jsonMartin
Copy link

@brettcannon I replaced the files for the Python plugin in my extension folder with the newest version from github, but that didn't seem to work for me. Perhaps there is another way to install the most recent development version of the plugin that I'm not using?

@DonJayamanne
Copy link

DonJayamanne commented Dec 1, 2017

That won't work, you need to run the compiler/transpiler.

@jsonMartin
Copy link

jsonMartin commented Dec 1, 2017 via email

@damufo
Copy link

damufo commented Apr 18, 2018

Hello:
I have same problem in debian stretch
Version 1.22.2
Commit 3aeede733d9a3098f7b4bdc1f66b63b0f48c1ef9
Date 2018-04-12T16:34:44.222Z
Shell 1.7.12
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64

ms-python.python: 2018.3.1 (29 Mar 2018)

Python script not start when control+F5 but from menu Debug->Start Without Debugging work fine.

@brettcannon
Copy link
Member

@damufo please open a separate issue.

@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

No branches or pull requests

7 participants