Why does vscode select global python as recommended environment?

[mkuurstra]

Hi,

Can I ask why the global python is used as the recommended environment instead of the environment configured by pipenv?

The order of preference mentioned here makes a lot of sense. I think that's also described here But for some reason I always need to change the interpreter and browse my ever growing list of virtual environments.

I'm not sure how long this has been bothering me but it might've been introduced with this issue. Any reason for this? Or something that might be causing this in my setup?

[brettcannon]

The order of preference is:

1. Environment local to the workspace
2. Global interpreter

We do that because environments outside of the workspace typically can't be tied back to the workspace they are meant to be used with, i.e. we would be probably guessing.

Although in pipenv's case we could potentially use pipenv --venv to tell us where to look if pipenv only supports a single environment per workspace (I'm also not sure if the act of asking would also trigger the creation of a virtual environment as well). If you happen to know the answer to these questions would you be up for opening a feature request?

[mkuurstra]

pipenv --venv doesn't create a new virtualenv, see the output below when executed in a directory without a virtualenv attached to it. As for multiple environments per workspace. As far as I know this isn't a feature of pipenv, I don't use pipenv that way and an online search doesn't return any results.

 $ pipenv --venv
No virtualenv has been created for this project(/Users/user) yet!
Aborted!

I'll see if I can open a feature request.

[mkuurstra]

See #19153