-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Starting debug only launches the activation of the conda environment but not the script #2862
Comments
I too am experiencing exactly this (Same version of vscode and vscode-python extension).
I am able to debug by exiting the terminal twice, but that is highly inconvenient. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
As a temporary work around, please disable the following setting in your user settings.json file: |
Solution:
|
Edit: DonJayamanne's solution is working, no need to use my workaround |
Duplicate of #2732 |
Issue Type: Bug
I simply launch VScode, and from there start my debug task. I've run a few debug task earlier today and it worked fine, but after updating to the latest python extension (I guess this is when it started), then I get this in the output window :
instead of the launch of the script.
Extension version: 2018.9.0
VS Code version: Code 1.28.0 (431ef9da3cf88a7e164f9d33bf62695e07c6c2a9, 2018-10-05T14:58:53.203Z)
OS version: Windows_NT x64 10.0.17134
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: