Skip to content

Conda run does not run the correct python interpreter #9432

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DonJayamanne opened this issue Jan 8, 2020 · 2 comments
Closed

Conda run does not run the correct python interpreter #9432

DonJayamanne opened this issue Jan 8, 2020 · 2 comments
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@DonJayamanne
Copy link

Originally reported by @mind6
https://github.com/microsoft/vscode-python/issues/8827#issuecomment-571840198

Environment data

  • VS Code version: 1.41.1
  • Extension version (available under the Extensions sidebar): XXX
  • OS and version: Windows
  • Python version (& distribution if applicable, e.g. Anaconda): 3.7.5
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): Conda
  • Relevant/affected Python packages and their versions: N/A
  • Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info How to update the language server to the latest stable version #3977): N/A

Expected behaviour

  • conda run -n <env name> python --version will run the python interpreter in the <env name> directory.

Actual behaviour

I'm on version 1.41 and it's already using "conda run", which doesn't work on my system. As you can see in the picture, the python version should be 3.8.0, but "conda run" only invokes the base environment python of version 3.7.5.
2020-01-08_084326

Steps to reproduce:

[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

  1. XXX

Logs

Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

XXX

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

XXX
@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug triage-needed Needs assignment to the proper sub-team labels Jan 8, 2020
@mind6
Copy link

mind6 commented Jan 8, 2020

sorry I duplicated the bug here: #9433

@brettcannon
Copy link
Member

Duplicate of #9433

@brettcannon brettcannon marked this as a duplicate of #9433 Jan 8, 2020
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jan 8, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Jan 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

3 participants