Open positopose opened 6 days ago
My guess is something is happening in VS code that's messing up the integrated terminal running the terminal command. And only on Mac.
This issue sounds like the same problem: https://github.com/microsoft/vscode/issues/230562
Not sure how uninstall/reinstall of the python extension can fix it, but two users reported that fixing their problem.
This issue too, but it sounds like it's been fixed: https://github.com/microsoft/vscode/issues/228191
I am pretty new to VSCode so sorry in advance if I am not providing enough information.
I am using macOS Sonorama 14.5 using VSCode with:
Version: 1.95.3 Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813 Date: 2024-11-13T14:50:04.152Z Electron: 32.2.1 ElectronBuildId: 10427718 Chromium: 128.0.6613.186 Node.js: 20.18.0 V8: 12.8.374.38-electron.0 OS: Darwin x64 23.5.0
While working with Python 3.13.0 from a virtual environment, if I try to run the following launch.json configuration:
{ "name": "main", "type": "debugpy", "request": "launch", "program": "${workspaceFolder}/src/main.py", "console": "integratedTerminal", "logToFile": true, "cwd": "${workspaceFolder}", "env": { "PYTHONPATH": "${cwd}" } }
I get the following error:
The debubpy extension logs are:
2024-11-17 03:40:49.650 [info] Resolving launch configuration with substituted variables 2024-11-17 03:40:49.656 [info] DAP Server launched with command: /Users/jorgepose/Desktop/Code/LearningPandas/.venv/bin/python /Users/jorgepose/.vscode/extensions/ms-python.debugpy-2024.10.0-darwin-x64/bundled/libs/debugpy/adapter --log-dir /Users/jorgepose/.vscode/extensions/ms-python.debugpy-2024.10.0-darwin-x64 2024-11-17 03:40:50.231 [info] Received 'debugpySockets' event from debugpy. 2024-11-17 03:40:50.237 [info] Received 'debugpySockets' event from debugpy. 2024-11-17 03:40:50.238 [info] Received 'debugpySockets' event from debugpy.
If I change the "console" to "internalConsole" I don't get such error and the code runs fine. I tried using previous versions of both vsCode and debugpy but that didn't work, and doing it while not having any other extension installed also gives the same error. From what I've seen in other issues, in Windows it's already fixed but I don't know if someone else is having this problem with Mac