Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Add support for Enthought Deployment Manager (EDM) #6874

Closed
@calabrian1598

Description

@calabrian1598

Similar to issue #4642. Trying to set settings.json to find some additional virtual environments. Mine are located in ~/.edm/envs (with 4 virtual environments under here, created by Enthought EDM). Have tried:

"python.venvPath": ".edm\envs"
"python.venvPath": "~\.edm\envs"
"python.venvPath": ".edm/envs"
"python.venvPath": "~/.edm/envs"
"python.venvPath": "C:\Users\user\.edm\envs"

VS Code does not find any of the virtual environments located in the ~/.edm/envs area. However, without having to modify python.venvPath it does find all three setup by Enthought Canopy in ~\AppData\Local\Enthought\Canopy\edm\envs. As far as I can tell, the virtual environment setup is the same in both areas.

In Issue #4642 found mention of python.venvFolders, so I tried the same variations as above:

"python.venvFolders" : [".edm\envs"]
"python.venvFolders" : [".edm/envs"]
...

No success.

Environment data

  • VS Code version: 1.36.1 (user setup)
  • Extension version (available under the Extensions sidebar): 2019.6.24221
  • OS and version: Windows_NT x64 10.0.17763
  • Python version (& distribution if applicable, e.g. Anaconda): Enthought Python 3
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): enthought EDM

Expected behaviour

Ability to select a Python environment in lower left corner, either immediately (see Issue #1458) or after restarting VS Code.

Actual behaviour

VS Code apparently does not find any of the virtual environments in ~/.edm/envs.

Steps to reproduce:

  1. Download EDM (https://www.enthought.com/product/enthought-deployment-manager/).
  2. Install EDM.
  3. Run "edm install --version 3 --environment test --yes" (Python 3 environment, no extra packages, yes to all prompts, environment named test).
  4. Verify there -- ~/.edm/envs/test
  5. Run VS Code.
  6. Open a Python file.
  7. Click on Python environment on lower left, verify that new "test" environment not present.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-environmentsFeatures relating to handling interpreter environmentsfeature-requestRequest for new features or functionality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions