- Restarting with stat
0.07s - Debugger warning: It seems that frozen modules are being used, which may
0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off
0.00s - to python to disable frozen modules.
0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to disable this validation.
0.97s - Error importing debugpy._vendored.force_pydevd (with sys.path entry: ‘c:\Users\Rafael\.vscode\extensions\ms-python.python-2022.20.0\pythonFiles\lib\python\debugpy\adapter/…/…\debugpy\launcher/…/…\debugpy/…’)
Traceback (most recent call last):
File “c:\Users\Rafael.vscode\extensions\ms-python.python-2022.20.0\pythonFiles\lib\python\debugpy_vendored\pydevd_pydevd_bundle\pydevd_defaults.py”, line 60, in on_pydb_init
ModuleNotFoundError: No module named ‘debugpy’
- Debugger is active!
- Debugger PIN: 115-345-752
This looks like a bug in the ms-python vs code extension, since it seems like they try to vendor debugpy, but then import it from a non-vendored name. But it seems like it would be fixed by a
pip install debugpy.