Change venvFolders to no longer be anchored to the user's home directory

We discovered during our bug bash that venvFolders exists but isn’t documented. Either we leave it, document it, and potentially not make (at least) our pyenv support depend on .pyenv being in it, or we remove the setting and use the documented functionality of pyenv directly.

[claytonlemons]

I ran across this issue because I have the following use case:

• rootWorkspaceDir (not relative to homeDir)
  • subProject1Dir
    • venvDIr
  • subProject2Dir
    • venvDIr

Making venvFolders not relative to the user’s home dir would allow me to specify each subproject once and easily switch between the corresponding environments as I switch between projects. The current workaround is to update venvPath or pythonPath each time I switch.

[leifwalsh]

What’s the current status of this? venvFolders and venvPath still exist, and are inconsistently documented:

• https://code.visualstudio.com/docs/python/environments#_where-the-extension-looks-for-environments only mentions venvPath
• https://code.visualstudio.com/docs/python/settings-reference#_general-python-settings only mentions venvFolders (but not the fact that it’s relative to your homedir)

I thought the original plan, to make venvPaths an array of entries like venvPath works today, and to get rid of venvFolders, made sense. It’s the least surprising (can be relative to ${workspaceFolder} or not), and supporting multiple entries makes it work with many tools, other filesystems mounted outside one’s home directory or project root, etc. It could be overridden in .code-workspace or settings.json files for projects to provide good defaults in source.

Did this ticket just get forgotten about? It would very much improve my company’s use cases to see this happen.