Skip to content

Activate conda environments using the path instead of the conda env name #3834

Closed
Closed
Activate conda environments using the path instead of the conda env name#3834
Assignees
karthiknadigkimadeline
Labels
area-environmentsFeatures relating to handling interpreter environmentsarea-terminalfeature-requestRequest for new features or functionality
Milestone
2019 November Sprint 1

Description

@NowanIlfideme
Anatoly Makarevich (NowanIlfideme)
opened on Jan 1, 2019

A project-local conda environment will be seen by VS Code, but it will fail to activate automatically. I would guess this is because it looks at the end of the path for the environment name and always activates by name, rather than by path. However, for environments created with the -p pathname flag, this will fail (as you can't even set environments name for them with -n).

Environment data

  • VS Code version: 1.30.1
  • Extension version (available under the Extensions sidebar): 2018.12.1
  • OS and version: Windows 10 V 1803
  • Python version: 3.7.0, conda 4.5.12
  • Type of virtual environment used: conda

Steps to reproduce:

  1. Create empty directory (mine was D:/TST) for project and add a random .py file (for ext to load), open in VS Code.
  2. Run conda create -p ./localenv python=3.7 in that directory.
  3. Select this environment as the Python interpreter.
  4. Make sure "python.terminal.activateEnvironment": true (or unset) in settings.
  5. Open new terminal (EDIT: as in interactive terminal, e.g. a REPL; for me, this was the cmd, but running code in the REPL has the same effect: it fails to activate the env, and thus runs in the default environment).

Expected behaviour

Automatic environment activation by path, rather than name:

D:\TST>activate ./localenv

(D:\TST\localenv) D:\TST>

OR

D:\TST>activate "D:\TST\localenv"

(D:\TST\localenv) D:\TST>

Actual behaviour

When opening a terminal:

D:\TST>activate localenv
Could not find conda environment: localenv
You can list all discoverable environments with `conda info --envs`.
D:\TST>

Activity

  1. ghost added
    triage-neededNeeds assignment to the proper sub-team
    on Jan 1, 2019

  2. NowanIlfideme commented on Jan 1, 2019

    @NowanIlfideme
    Anatoly Makarevich (NowanIlfideme)
    on Jan 1, 2019
    Author

    Note that all conda environments made with the -p argument will fail this way.

    Also, the environment docs show this working with the virtualenv, but it has conda directly next to it (second image). I understand if this is just in the "not yet implemented" territory (I've read that you've been seeking to talk more closely with the Anaconda team), just slightly misleading as it currently is shown.

  3. Derek Keeler (d3r3kk)
    assigned
    Eric Snow (ericsnowcurrently)
    on Jan 2, 2019
  4. Derek Keeler (d3r3kk)
    added
    triage
    on Jan 2, 2019
  5. ghost removed
    triage-neededNeeds assignment to the proper sub-team
    on Jan 2, 2019

  6. ericsnowcurrently commented on Jan 9, 2019

    @ericsnowcurrently
    Eric Snow (ericsnowcurrently)
    on Jan 9, 2019

    Hi Anatoly Makarevich (@NowanIlfideme). Thanks for letting us know about this. I wasn't able to duplicate the issue just by opening a (Python) terminal. However, I did see the problem when opening a REPL. We'll investigate further.

  7. Eric Snow (ericsnowcurrently)
    added
    bugIssue identified by VS Code Team member as probable bug
    needs PR
    area-terminal
    feature-interpreter
    and removed
    triage
    on Jan 9, 2019
  8. Eric Snow (ericsnowcurrently)
    removed their assignment
    on Jan 9, 2019

  9. faroit commented on Mar 14, 2019

    @faroit
    Fabian-Robert Stöter (faroit)
    on Mar 14, 2019

    This issue is does also trigger a problem when using the "install linter" command

  10. gonzalocasas commented on Mar 15, 2019

    @gonzalocasas
    Gonzalo Casas (gonzalocasas)
    on Mar 15, 2019

    I am seeing the same issue with local conda environments created with prefix (e.g. -p ./env). Discovery works but then activation fails every time I open a new terminal (cmd in my case).

  11. sindzicat commented on Mar 27, 2019

    @sindzicat
    Sindzicat (sindzicat)
    on Mar 27, 2019

    The same problem.

  12. 24 remaining items

  13. Karthik Nadig (karthiknadig)
    modified the milestones: 2019 October Sprint 2, 2019 October Sprint 3 on Oct 23, 2019
  14. Karthik Nadig (karthiknadig)
    self-assigned this
    on Nov 2, 2019
  15. Brett Cannon (brettcannon)
    changed the title [-]Activate coda environments using the path instead of the conda env name[/-] [+]Activate conda environments using the path instead of the conda env name[/+] on Nov 5, 2019
  16. Karthik Nadig (karthiknadig)
    added
    in progress
    on Nov 5, 2019
  17. Karthik Nadig (karthiknadig)
    modified the milestones: 2019 October Sprint 3, 2019 November Sprint 1 on Nov 6, 2019
  18. Karthik Nadig (karthiknadig)
    added
    in review
    and removed
    in progress
    in review
    on Nov 7, 2019
  19. Karthik Nadig (karthiknadig)
    assigned
    Kim-Adeline Miguel (kimadeline)
    on Nov 11, 2019

  20. kimadeline commented on Nov 12, 2019

    @kimadeline
    Kim-Adeline Miguel (kimadeline)
    on Nov 12, 2019

    ✅ Validated using 2019.12.48501-dev

  21. Kim-Adeline Miguel (kimadeline)
    closed this as completedon Nov 12, 2019
  22. ghost removed
    needs PR
    on Nov 12, 2019
  23. lock
    locked as resolved and limited conversation to collaborators on Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

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

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions