Please use interpreterPath instead pythonVenv

[danielniccoli]

The extension should use the configured interpreter path python.interpreterPath instead of an addition custom variable azureFunctions.pythonVenv.

[alexweininger]

This sounds like a good suggestion. In my Python settings I see a python.venvPath setting? Did you mean to suggest that?

[danielniccoli]

No, I mean python.interpreterPath. It is set anyway in the project and removes the need to configure yet another setting explicitly. It also reduces

"command": "${config:azureFunctions.pythonVenv}\\Scripts\\python -m pip install -r requirements.txt"

to

"command": "${command:python.interpreterPath} -m pip install -r requirements.txt"

[nturinski]

I was investigating this one, and there's an annoying issue as to why this won't work for us.

It seems like if python.interpreterPath has a space in it, it won't actually run the python command for us.

You end up with something like this:

Works fine without a space though.

This might be a windows only issue for now. I'm trying to see if there's a way for me to get the interpreter in our runtime code so that we can convert it, but I think it'd be better if the Python team just wrapped their fs path with quotations.

I have an issue tracking it here: microsoft/vscode-python#23028