Repository navigation
Starting debug only launches the activation of the conda environment but not the script #2862
Description
Activity
I too am experiencing exactly this (Same version of vscode and vscode-python extension).
Windows PowerShell Copyright (C) Microsoft Corporation. Tous droits réservés. PS C:\Users\oueal\Documents\Projects\test> & cmd /k "C:\Users\oueal\AppData\Local\Continuum\anaconda3\Scripts\activate base & powershell" Windows PowerShell Copyright (C) Microsoft Corporation. Tous droits réservés. PS C:\Users\oueal\Documents\Projects\test> exit (base) C:\Users\oueal\Documents\Projects\test>exit PS C:\Users\oueal\Documents\Projects\test> cd 'c:\Users\oueal\Documents\Projects\test'; ${env:PYTHONIOENCODING}='UTF-8'; ${env:PYTHONUNBUFFERED}='1'; & 'C:\Users\oueal\AppData\Local\Continuum\anaconda3\python.exe' 'c:\Users\oueal\.vscode\extensions\ms-python.python-2018.9.0\pythonFiles\experimental\ptvsd_launcher.py' '50089' 'c:\Users\oueal\Documents\Projects\test\test.py' Hello world! PS C:\Users\oueal\Documents\Projects\test>I am able to debug by exiting the terminal twice, but that is highly inconvenient.
As a temporary work around, please disable the following setting in your user settings.json file:
"python.terminal.activateEnvironment": falseReacted by YutongWang- added this to the 2018, week 40 - October Sprint 1 milestone
on Oct 11, 2018 Solution:
- Open, activate and launch the debugger process in the terminal our selves, rather than passing this onto VSC.
- This way, we can pass the activation script and run the debugger command in one go (combine the commands).
Reacted by Derek Keeler, AlexandreOuellet, q3ccn and Julio Cesarworkaround : You can install the older extension version. You can download the vsix here : https://github.com/Microsoft/vscode-python/releases/tag/2018.8.0
Make sure you disabled autoUpdate for extensions thoughEdit: DonJayamanne's solution is working, no need to use my workaround
Reacted by Shevach MarantsDuplicate of #2732
- marked this as a duplicate of Timeout waiting for debugger connection when using Windows PowerShell #2732
on Oct 16, 2018 - locked as resolved and limited conversation to collaborators
on Nov 13, 2018
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