Python extension hangs on loading

[AdamCummick]

Environment data

• VS Code version: 1.57.1
• Extension version (available under the Extensions sidebar): v2021.6.944021595
• OS and version: Windows 10 build 19042
• Python version (& distribution if applicable, e.g. Anaconda): 3.8
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
• Relevant/affected Python-related VS Code extensions and their versions: Pylance 2021.6.3
• Value of the python.languageServer setting: Pylance

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]

Expected behaviour

Python extension loads

Actual behaviour

Python extension hangs on loading indefinitely

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

1. Open VSCode, extension begins loading and hangs immediately.
   • Disabling then re-enabling extensions did not correct issue
   • Uninstalling and re-installing extensions did not correct issue

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

User belongs to experiment group 'pythonaa'
User belongs to experiment group 'pythonJoinMailingListVar2'
User belongs to experiment group 'pythonJediLSP'
User belongs to experiment group 'pythonDiscoveryModuleWithoutWatcher'
User belongs to experiment group 'pythonTensorboardExperiment'
User belongs to experiment group 'pythonSurveyNotificationcf'
User belongs to experiment group 'PythonPyTorchProfiler'
Python interpreter path: ~\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\python.exe

[brettcannon]

Did you set the Python interpreter path manually in your settings? That path is to the Windows Store install of Python in a special Windows directory that we explicitly try not to set.

[AdamCummick]

I don't recall manually changing it.
It's the same path I see for my default system interpreter (i.e. print(sys.executable))

[AdamCummick]

Looking into it further, it appears that this only occurs when using a file on a USB drive. Files on the local disk have the extension load without issue. I did select to trust the locations in both cases.

Additionally, I changed the interpreter location to Python interpreter path: ~\AppData\Local\Programs\Python\Python39\python.exe and it did not change behaviour.

[brettcannon]

The Windows Store install is a bit weird -- due to how Windows Store apps are sandboxed -- as there's the path to the thing you're supposed to execute, and then the actual thing that gets run (the latter is what you're seeing in your output and with sys.executable).

And that second path you specified is a different version than the first one you specified.

You obviously are loading to some point, so are you able to launch the environment picker? Basically what is giving the impression of the extension hanging?

[AdamCummick]

And that second path you specified is a different version than the first one you specified.

Right, I changed the path away from the windows store path because it was unusual. It did not correct anything.

You obviously are loading to some point, so are you able to launch the environment picker? Basically what is giving the impression of the extension hanging?

I get this on load and I cannot get into the environment picker.

It seems this issue only happens when I'm editing files on a USB drive. If I'm editing files on my local disk, the extension loads correctly.

[brettcannon]

Is it an especially fast or slow USB drive? Basically VS Code has a timer to try and call out bad extensions that are slow. It's possible that the interactions we do with a workspace when we launch is too slow on your USB drive for us to not trigger the warning.

[AdamCummick]

I've tried a couple USB drives, they aren't especially slow or fast. The extension has worked previously on them without issue on multiple PCs.