You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried several times to reinstall the extension. Doesn't help.
I have a lot of extensions installed, But I've disabled all and only ms-python is enabled.
Finally, launch the extension using the Launch Extension from the Debugger
If the extension does not load, you'll get errors in the debugger console, and that's what we're interested in. If it does work, then we could try something else.
I've passed all the steps from the instruction and got the following error:
Changing settings in the local workspace for "editor.detectIndentation" doesn't help.
Secon window is closing after I open *.py code or try to open "Python: Select Interpreter" in command palette:
In the extension's debugger window I am getting the following exception (if it will help):
Flo (@mawenzy) Awesome!!! Thanks a lot for your solution. It worked for me. Now, I can sleep in peace.
In my case mingw path had semicolon in the path variables. How did you find this solution?
Flo (@mawenzy)Ayanjit can either of you provide your PATH settings before and after? Semi-colons are the path separator on Windows so that shouldn't cause a problem (but we have had issues with PATH and node previously). But if we can have an example of where it does and does not work we can also track down where we need to be careful about this sort of thing.
Brett Cannon (@brettcannon) adding a semicolon to a path results in this particular path to be written in quotations marks, so usually it looks like this: PATH=path1;path2;path3
But when for example path2 has a semicolon in it, is reads: PATH=path1;"path2";path3
Flo (@mawenzy) Ah, so you had a directory like C:\I\like\semi;colons and it ended up as PATH=path1;"C:\I\like\semi;colons";path3? And then making it PATH=path1;path3 solved it?
Flo (@mawenzy) Thanks, it solves my issue!
for my case, when I type "path" in cmd, results contain path with "", like PATH=path1;"path2";path3...
I find one cases may cause this issue, that is using alias path, such as %CUDA_PATH%;%CUDA_SDK_PATH%. After I replaced alias path with full path, issue disappeared.
Activity
DonJayamanne commentedon Dec 4, 2017
Please try reinstalling the extension. Also, do you have other installed on the current system?
OraCool commentedon Dec 5, 2017
Tried several times to reinstall the extension. Doesn't help.
I have a lot of extensions installed, But I've disabled all and only ms-python is enabled.
Zedonboy commentedon Dec 13, 2017
Any solution Yet?
brettcannon commentedon Dec 13, 2017
Unfortunately not because the error is "it crashed" which doesn't help debug why the extension crashed.
DonJayamanne commentedon Dec 13, 2017
OraCool (@OraCool) are you able to help us diagnose this issue by debug this at your end?
I could send the instructions for this. Thanks
OraCool commentedon Dec 15, 2017
I can help if needed. Please let me know what should I do
DonJayamanne commentedon Dec 16, 2017
OraCool (@OraCool)
One last thing, please could you try disabling all other extensions and testing this out.
Here are the instructions:
If the extension does not load, you'll get errors in the debugger console, and that's what we're interested in. If it does work, then we could try something else.
OraCool commentedon Dec 18, 2017
I've passed all the steps from the instruction and got the following error:



Changing settings in the local workspace for "editor.detectIndentation" doesn't help.
Secon window is closing after I open *.py code or try to open "Python: Select Interpreter" in command palette:
In the extension's debugger window I am getting the following exception (if it will help):
127 remaining items
Ayanjit commentedon May 16, 2018
Flo (@mawenzy) Awesome!!! Thanks a lot for your solution. It worked for me. Now, I can sleep in peace.
In my case mingw path had semicolon in the path variables. How did you find this solution?
DonJayamanne commentedon May 16, 2018
OraCool (@OraCool) Jingsong Xu (@xjsxujingsong) Jingsong Xu (@xjsxujingsong)
Please could you also check if you have similar (#342 (comment)) invalid entries in your current path variable.
brettcannon commentedon May 16, 2018
Flo (@mawenzy) Ayanjit can either of you provide your
PATHsettings before and after? Semi-colons are the path separator on Windows so that shouldn't cause a problem (but we have had issues withPATHand node previously). But if we can have an example of where it does and does not work we can also track down where we need to be careful about this sort of thing.mawenzy commentedon May 16, 2018
Brett Cannon (@brettcannon) adding a semicolon to a path results in this particular path to be written in quotations marks, so usually it looks like this:
PATH=path1;path2;path3But when for example path2 has a semicolon in it, is reads:
PATH=path1;"path2";path3brettcannon commentedon May 16, 2018
Flo (@mawenzy) Ah, so you had a directory like
C:\I\like\semi;colonsand it ended up asPATH=path1;"C:\I\like\semi;colons";path3? And then making itPATH=path1;path3solved it?mawenzy commentedon May 16, 2018
Yes, exactly
brettcannon commentedon May 16, 2018
Flo (@mawenzy) Great, thanks for this! We will see if it's on our end, VS Code, or Node's.
xjsxujingsong commentedon May 17, 2018
Don Jayamanne (@DonJayamanne) Just checked that. It works fine now. I accidentally add an additional ";" in the path variable. Thanks!!
vinjohn commentedon May 21, 2018
Flo (@mawenzy) Thanks, it solves my issue!
for my case, when I type "path" in cmd, results contain path with "", like PATH=path1;"path2";path3...
I find one cases may cause this issue, that is using alias path, such as %CUDA_PATH%;%CUDA_SDK_PATH%. After I replaced alias path with full path, issue disappeared.
arjunkharbanda commentedon May 21, 2018
DonJayamanne commentedon May 21, 2018
Arjun Kharbanda (@arjunkharbanda)
about:blankin there. Please edit your environment variables to remove invalid items such as the one above and any empty lines.;;(replace with;)."that do not seem to have matching closing"Once again, remove invalid items, by editing you PATH environment variable.
arjunkharbanda commentedon May 21, 2018
looks like the issue is resolved it's is due to invalid values in
PATHin environment variables. Can it be fixed in future updates?d3r3kk commentedon May 22, 2018
Closing, we will track issue #1698 that will resolve this issue from our end.