Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debug tool is not working on recent versions #19555

Closed
miguelomp opened this issue Jul 26, 2022 · 5 comments
Closed

Debug tool is not working on recent versions #19555

miguelomp opened this issue Jul 26, 2022 · 5 comments
Labels
triage-needed Needs assignment to the proper sub-team

Comments

@miguelomp
Copy link

I 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

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Jul 26, 2022
@gao-keyong
Copy link

same behavior on ubuntu 18.04.2 LTS

@JPeMu
Copy link

JPeMu commented Jul 26, 2022

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 #19482 (The latest debugger requires Python >= 3.7 but fails silently when used on an older version).

@miguelomp
Copy link
Author

Yes, I just confirm the code I was trying to debug is in python 3.6

But is it ok to kill the support for older versions of Python 3? as suggested in #19482

@brettcannon
Copy link
Member

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 (#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.

@brettcannon brettcannon closed this as not planned Won't fix, can't repro, duplicate, stale Jul 26, 2022
@miguelomp
Copy link
Author

Thank you!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
triage-needed Needs assignment to the proper sub-team
Projects
None yet
Development

No branches or pull requests

4 participants