Breaks python locator on mapped drives in Windows

[arthurgailes]

Hello,

The addition of Python Environments prevents the python extension (as well as vscode/select interpreter) from recognizing virtual conda environments on mapped drives. This feature is currently enabled by setting Python Locator to 'js', from native. Uninstalling Python Environments resolves the issue.

See also: microsoft/python-environment-tools#194

With Python Environments:

After uninstalling:

[eleanorjboyd]

Thanks for the issue report- will have to review to make sure the envs ext supports "virtual conda environments on mapped drives"

[eleanorjboyd]

Can you try running:

1. "Python: Run Python Environment Tool (PET) in Terminal..." and do discovery, see if the env you want is there
2. given the env you want, go to "Python: Run Python Environment Tool (PET) in Terminal..." and select "resolve" and paste it there. Does it resolve to a different path than suggested?

[arthurgailes]

It produces an error.

 "L:\DataSets9\arthur\programs\VSCode-win32-x64-1.104.3\data\extensions\ms-python.v
scode-python-envs-1.8.0-win32-x64\python-env-tools\bin\pet.exe" find --verbose
At line:1 char:147
+ ... ython-envs-1.8.0-win32-x64\python-env-tools\bin\pet.exe" find --verbo ...
+                                                              ~~~~
Unexpected token 'find' in expression or statement.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnexpectedToken

[arthurgailes]

bumping