debugger not working after fresh install (tried twice)

[noferusername]

Environment data

Please check: microsoft/vscode#82322 (comment)

CPUs	Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 x 2712)
GPU Status	2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled
Load (avg)	undefined
Memory (System)	31.91GB (25.36GB free)
Process Argv
Screen Reader	no
VM	0%

Extension | Author (truncated) | Version
python | ms- | 2019.10.41019

Expected behaviour & Actual behaviour

Debugger runs but no variables show up. Everything is freshly installed. I did no changes, anything. I simply try it on a simple code and does nothing

I originally created bug report on microsoft/vscode, they closed and recommended opening here. (microsoft/vscode#82322 (comment))

Steps to reproduce:

1. Install VSCODE with the default Python Extension
2. write a simple code (see attached) to test the debugger
3. nothing happens

[kvaldec]

Same problem here.

It worked two or three days ago; also worked on Insiders (Python remote debugging).

Version: 1.39.1
Commit: 88f15d17dca836346e787762685a40bb5cce75a8
Date: 2019-10-10T23:35:11.314Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 17.7.0

Intel Core 2 Duo 3,06 GHz, macOS High Sierra 10.13.6 (17G65).

[kvaldec]

I kind of got it to work, and this is how.

Python 2.7 is also installed on the machine (as is 3.5, and 3.7). I'm trying to work with v3.7.4. But, this change in launch.json made it work:

...
"pythonPath" : "/usr/bin/python"
...

So, setting the pytonPath explicitly to what is actually Python 2.7.10 on my machine made the debugger start, and it seems to be working fine.

Not sure if this is completely ok. But setting it explicitly to any other Python binary makes it not even start.

[OlafEichstaedt]

debugger stopped working, probably after update to 2019.10.41019

1. open a py file

2. set a breakpoint

3. F5

4. debug action bar appears, then disappears

5. no output in debug console (even from code before the breakpoint)

6. tried to roll back 2019.10.41019 to previous version, but did not get any suggestions for previous versions.

7. uninstalled 2019.10.41019,

8. reinstalled 2019.10.41019, no change, debugger still not working

9. but at least now I can roll back to 2019.9.34911: with 2019.9.34911, debugger works as expected

using conda env as python backend which creates sys.path as follows:
['c:\Users\me\where_my_pyfile_is',
C:\Users\me\Anaconda3\envs\python37\python37.zip', 'C:\Users\me\Anaconda3\envs\python37\DLLs', 'C:\Users\me\Anaconda3\envs\python37\lib',
'C:\Users\me\Anaconda3\envs\python37', 'C:\Users\me\Anaconda3\envs\python37\lib\site-packages']

[karthiknadig]

this is likely due to #7836. See comment here for possible work around: #7836 (comment)

[karthiknadig]

Closing this since the fix is tracked via #7836