Detect virtual environments created by tox

[brettcannon]

If you're using tox then the tool will create multiple virtual environments for you that editable install your code. Picking those up for use to negate having to create duplicate virtual environments would be helpful.

[varungbt]

second that as well..

[gaborbernat]

Any plans/progress on this?

[gaborbernat]

Even though https://code.visualstudio.com/docs/python/environments#_where-the-extension-looks-for-environments says it looks in the workspace, it does not pick up stuff from under the .tox folder.

[gaborbernat]

Setting: "python.venvPath": "${workspaceFolder}/.tox" seems to do the trick.

[brettcannon]

The docs say that we search for virtual environments "located directly under the workspace (project) folder", which means a .tox directory doesn't work because there is yet another directory level for each Python version that tox uses (hence why this issue is still open).

And your temporary solution does work.

[brettcannon]

To help manage our issues and to better communicate what the team plans to work on we are closing issues that we don't plan to work on but would accept a pull request from a volunteer for. To be clear, closing this issue does not mean we won't consider a pull request for this enhancement as outlined in our contributing guide, just that the development team has no plans to work on it themselves.