3 ms·

ahh, sorry. that wasn't clear because i haven't used the python debugger in visual studio code and don't use python in general. i would guess my hunch that thi

ahh, sorry. that wasn't clear because i haven't used the python debugger in visual studio code and don't use python in general. i would guess my hunch that this is a python problem is correct. i use ionide for f#. i am wondering if i point ionide (if it's possible) to use f# running on ubuntu through wsl, will its type inference, linting, autocompletion, etc. still work?

shawnz 8y ago
It's not a python problem. Like I said, when you initiate a debug session, VS code will launch the python binary just fine, but it passes it the Windows path of the file you're debugging which obviously the WSL python binary can not understand. I assume F# on WSL would have the same issue, although I haven't tried personally. Here you can see a bug report for the issue: https://github.com/Microsoft/vscode-python/issues/67 https://github.com/Microsoft/vscode-python/issues/67 And the same issue for other languages: https://github.com/Microsoft/vscode/issues/22663 https://github.com/Microsoft/vscode/issues/22663 https://github.com/Microsoft/vscode-go/issues/926 https://github.com/Microsoft/vscode-go/issues/926 Looks like they've implemented fixes for C++ and nodejs though: https://github.com/Microsoft/vscode-cpptools/issues/85#issuecomment-277128833 https://github.com/Microsoft/vscode-cpptools/issues/85#issue... https://github.com/Microsoft/vscode/issues/39144#issuecomment-347310763 https://github.com/Microsoft/vscode/issues/39144#issuecommen...