Configured debug type "python" is not supported for VS Code

10,200

Solution 1

I had the same problem and was able to solve it by uninstalling Python and Jupyter Notebook extensions in VS Code and then re-installing them. Note that Jupyter Notebook is now required to use the Python extension in VS Code.

Solution 2

This issue is a VS Code bug, it is being solved in an early Dec-2021 release (v1.63). The warning has no effect whatsoever, there are no real issues running the code. So, don't pay attention to it, it will be fixed in a short time.

Edit note: Adding, removing, installing, or disabling/enabling the Jupyter Notebook and its related extensions seem to solve the problem but only until the next VS Code restart.

Share:
10,200
user3841581
Author by

user3841581

Updated on June 15, 2022

Comments

  • user3841581
    user3841581 almost 2 years

    I have issues debugging with VS code. I have installed python for vs code extension and reloaded it several time. But when I tried to run in the debug mode, I have the following error

    The debug type is not recognized. Make sure that you have a corresponding debug extension installed and that it is enabled.
    

    My launch.json has the following contain

    {
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        
        {
            "name": "Python : Fichier actuel",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal"
        }
    ]
    }
    

    What could be the issue?

  • jsf80238
    jsf80238 almost 3 years
    I was using open source Codium and the Python extension was not installed out-of-the-box.
  • ChrisProsser
    ChrisProsser over 2 years
    Uninstalling Jupyter seemed to fix it for me, but then the problem was back the next day when I started vscode again.
  • Paul P M
    Paul P M over 2 years
    @ChrisProsser - same here. After closing/reopening vs code. No issues running the config though. Only being flagged in the edtor
  • Alejandro QA
    Alejandro QA over 2 years
    I can confirm that release v1.63 fixed the issue.