microsoft / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
162.63k stars 28.67k forks source link

Can't debug Django applications any longer #52121

Closed asandeep closed 6 years ago

asandeep commented 6 years ago

Issue Type: Bug

Hi Team, I am no longer able to debug my Django applications in VSCode. I tried both existing configuration and new experimental configurations and none of them really work. When I use normal config (given below), django server starts but all breakpoints converts to: 'Unverified breakpoint' and code never stops on the set breakpoints.

{
            "name": "Django",
            "type": "python",
            "request": "launch",
            "program": "${workspaceFolder}/manage.py",
            "args": [
                "runserver",
                "--noreload",
                "--nothreading"
            ],
            "debugOptions": [
                "RedirectOutput",
                "Django"
            ]
        }

With experimental config, django server never starts and all i get in console is this message:

pydev debugger: starting

pydev debugger: New process is launching (breakpoints won't work in the new process). pydev debugger: To debug that process please enable 'Attach to subprocess automatically while debugging?' option in the debugger settings.

Experimental config:

           {
            "name": "Django Experimental",
            "type": "pythonExperimental",
            "request": "launch",
            "program": "${workspaceFolder}/manage.py",
            "args": [
                "runserver",
                "--noreload",
                "--nothreading",
            ],
            "django": true,
        }

VS Code version: Code 1.23.1 (d0182c3417d225529c6d5ad24b7572815d0de9ac, 2018-05-10T16:04:33.747Z) OS version: Linux x64 4.4.0-128-generic

System Info |Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2469)| |GPU Status|2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: disabled_software
video_decode: unavailable_software
video_encode: enabled
vpx_decode: unavailable_software
webgl: enabled
webgl2: enabled| |Load (avg)|1, 1, 1| |Memory (System)|7.66GB (0.38GB free)| |Process Argv|/snap/vscode/37/usr/share/code/code| |Screen Reader|no| |VM|0%|
Extensions (24) Extension|Author (truncated)|Version ---|---|--- rainbow-brackets|2gu|0.0.6 material-icon-theme|PKi|3.5.0 code-settings-sync|Sha|2.9.2 Bookmarks|ale|0.19.1 scratchpad|awe|0.1.0 vscode-eslint|dba|1.4.12 vscode-babel-coloring|dza|0.0.4 gitlens|eam|8.3.5 auto-rename-tag|for|0.0.15 ginfuru-vscode-jekyll-syntax|gin|0.0.5 node-module-intellisense|lei|1.5.0 terraform|mau|1.1.2 vscode-cosmosdb|ms-|0.7.2 python|ms-|2018.5.0 azure-account|ms-|0.4.0 debugger-for-chrome|msj|4.6.0 color-highlight|nau|2.3.0 quicktype|qui|10.0.24 gi|rub|0.2.11 guides|spy|0.9.2 code-spell-checker|str|1.6.10 vscode-ansible|vsc|0.2.6 JavaScriptSnippets|xab|1.6.0 markdown-all-in-one|yzh|1.4.0
weinand commented 6 years ago

Please file this issue against the Python extension.

vscodebot[bot] commented 6 years ago

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines.

Happy Coding!