Unable to debug python with node 13 environment. "Number of constructor arguments..." #105
Comments
|
You need to use node < 13. I recommend nvm use 10 This is a bug/incompatibility of the python debug adapter from Microsoft |
|
The debugger works in vscode though, is that expected with node > 13? |
|
I expect vscode is bundling node. You need a version of node that will run the DA. |
|
All vimspector is doing is running this: If you can see vscode doing something different let me know. |
|
re-opening as this doesn't affect VSCode and there's a meaninful possibility that https://github.com/microsoft/vscode-python/issues/9829 won't be fixed. |
|
There is however a workaround, you can use You'll have to work out the |
|
Thanks, I'll take a look at this later |
|
I might take a look at configuring it myself, but I didn't understand much of what was being said in the ptvsd thread, so it'll be a dedicated project in itself some other time. Is there much chance you will end up switching it yourself once the standalone version is released? |
puremourning
changed the title
|
Here's how to make it work with Alternative: Use debugpy directlyIf you can't get a node 10 envirinment set up for whatver reason, then you can Here's how:
{
"adapters": {
"debugpy": {
"command": [
"python",
"-m",
"debugpy.adapter"
],
"name": "debugpy",
"configuration": {
"python": "python"
}
}
}
}Then in theory you should just have to change I tested this and it works for me. |
|
Thank you! |
|
I understand that neovim isn't really supported, but this particular adapter worked fine on vim but not neovim. Are you willing to offer any suggestions? |
|
Please see the note in the README. |
|
It’s a(nother) neovim missing feature. Apparently it works with master but 🤷♂️ |
|
I pushed a PR to make it work in neovim. le sigh. |
|
Way of the future |
|
TL;DR TLDR (Vim only, no NeoVim)
Paste and save:
|
|
Why? Or just use vimspector to install debugpy. What is the purpose of all that effort? |
Describe the bug
Starting to debug a basic python file opens vimspector windows but no debugging starts. Vimspector encounters an error and crashes.
To Reproduce
vim test.pyiprint('hello')<f5>Vimspector config file:
{ "configurations": { "univisal: Launch": { "adapter": "vscode-python", "configuration": { "name": "<name>: Launch", "type": "python", "request": "launch", "cwd": "${workspaceRoot}", "stopOnEntry": true, "console": "externalTerminal", "debugOptions": [], "program": "${file}" } } } }Expected behavior
A debugging session starts
Actual behaviour
Vimspector windows open but no debugging starts.
No output except stderr, and that was the same as the contents of the log.
Environemnt
git rev-parse HEADif cloned or thename of the tarball used to install otherwise)
c6c0144
vim --versionornvim --versionwhich vimorwhich nvim:Output of
:py3 pass: no outputOutput of
:py3 import vim: No outputOperating system: Arch linux updated today
Vimspector.log:
The text was updated successfully, but these errors were encountered: