Debug tool is not working on recent versions
See original GitHub issueI have VScode remotely to debug python code. The launch.json is ok, I already used in the past but now it stopped working.
I had to rollback the version of python extension to v2022.4.0 and now is working. I tested in the 3 most recent versions but it is not working.
My env:
- some remote server with vscode
- python and pylance extensions installed in remote server
- remote server OS: ubuntu 18.04.2 LTS
My launch config
{
"name": "some-project",
"type": "python",
"request": "launch",
"python": "/home/ubuntu/.local/share/virtualenvs/some-project-pipenv-loc/bin/python",
"program": "/home/ubuntu/some-project/test_main.py",
"console": "integratedTerminal",
"envFile": "/home/ubuntu/some-project/.env",
"cwd": "/home/ubuntu/some-project/",
"justMyCode": true
}
Let me know if extra information is needed.
Thanks in advance
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:5 (1 by maintainers)
Top Results From Across the Web
django-debug-toolbar not showing up - Stack Overflow
I found that the latest version from git resulted in an ImproperlyConfigured error when running through nginx/uwsgi. Either way, if you want to...
Read more >How to use the Debug Diagnostics tool to troubleshoot a ...
Click Start, click Run, type the path of the Debug Diagnostics tool, and then click OK. Note By default, the Debug Diagnostics tool...
Read more >Fix list for Debug Tool Plug-ins - IBM
This document contains a complete listing of Debug Tool Plug-in fixes with the most recent fix at the top.
Read more >Troubleshooting common PHP debugging issues | PhpStorm ...
Troubleshooting common PHP debugging issues ... php --version ... session is started and opens the Debug tool window automatically.
Read more >Installation — Django Debug Toolbar 3.8.1 documentation
If you're upgrading from a previous version, you should review the change log ... You can change the logic of determining whether or...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
In the latest release of debugpy, support for Python versions older than 3.6 was dropped as Python 3.6 is not supported upstream since last year by the Python development team (this is also the support promise the Python extension itself follows as mentioned in our README). Based on the age of Ubuntu LTS that everyone is running, my assumption is you’re all still running Python 3.6 (or older).
We are discussing/planning on breaking out debugging support into its own extension (https://github.com/microsoft/vscode-python/issues/19559). That would allow us to do an initial release using debugpy 1.5 which you all can pin to, but then allow the Python extension to update as normal (as long as it happens to support your older Python versions). Feel free to subscribe to that issue, follow our blog at https://aka.ms/pythonblog, or follow the VS Code release notes where we would announce any new extension.
Same issue for me. Neither of the 2022.10.x versions work for me, but reverting to 2022.8.1 did re-enable debugging. I’m using an old version of Python (3.6.8) installed via pyenv on Linux Mint 20.2 (Uma) based on Ubuntu Focal (20.04).
I guess it’s related to https://github.com/microsoft/vscode-python/issues/19482 (The latest debugger requires Python >= 3.7 but fails silently when used on an older version).