Allow Activated Virtual Envs to Be Detected w/ a Workspace File by tgrue-openai · Pull Request #25141 · microsoft/vscode-python
Addresses #25140 (which I just filed).
- Removed the check that a workspaceFile isn't used when looking for Activate Virtual Envs
- Adds a debug log to help make other forms of early exit.
Of note, I'm not sure if the existing traceVerbose('VS Code was not launched from the command line'); is correct.
As far as I can tell, workspaceFile != multiroot workspaces. I'm not sure why this check previously existed. I don't know if this might cause others problems; but right now this check causes a lot of challenge for our workflow.