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.

Sign up for GitHub

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

Jump to bottom

Error "Cannot read property 'openConfigFile' of undefined" when starting python program without the debugger #32

Closed
AlanGillespie opened this issue Nov 10, 2017 · 3 comments
Closed

Error "Cannot read property 'openConfigFile' of undefined" when starting python program without the debugger #32

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

Comments

@AlanGillespie
Copy link

Environment data

VS Code version: 1.18.0
Python Extension version: 0.8.0
Python Version: 2.7.14
OS and version: Windows 10

Actual behavior

Press Ctrl+F5 to start a python program without the debugger, and VS Code displays the error
"Cannot read property 'openConfigFile' of undefined"

F5 to start with the debugger works fine.

Expected behavior

Should just start the program. It always did with Python Extension 0.7.0, which I had been using for some time.

Steps to reproduce:

Start any python program inside version 0.8.0 of this extension, without the debugger.

Logs

No output
@Agnpalm
Copy link

Agnpalm commented Nov 10, 2017

This is the same as issue #25

@brettcannon brettcannon added awaiting 1-verification area-debugging bug Issue identified by VS Code Team member as probable bug labels Nov 14, 2017
@brettcannon
Copy link
Member

@Agnpalm we think this is a slightly different case.

@DonJayamanne
Copy link

Duplicate of #25

@DonJayamanne DonJayamanne marked this as a duplicate of #25 Nov 16, 2017
@DonJayamanne DonJayamanne mentioned this issue Nov 16, 2017
Merged
@DonJayamanne DonJayamanne added this to the December 2017 milestone Nov 17, 2017
DonJayamanne added a commit that referenced this issue Nov 22, 2017
@DonJayamanne
Fix issues when running without debugging and debugged code terminates (
a6b49d2 
#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
@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.
Assignees
No one assigned
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Milestone
December 2017
Development

No branches or pull requests
4 participants
@brettcannon @DonJayamanne @AlanGillespie @Agnpalm