Skip to content
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

Wrong display name for current interpreter #3532

Closed
syagev opened this issue Dec 3, 2018 · 2 comments
Closed

Wrong display name for current interpreter #3532

syagev opened this issue Dec 3, 2018 · 2 comments

Comments

@syagev
Copy link

syagev commented Dec 3, 2018

Environment data

  • VS Code version: 1.29.1
  • Extension version (available under the Extensions sidebar): 2018.11.0
  • OS and version: Windows 10
  • Python version (& distribution if applicable, e.g. Anaconda): 3.5.4
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pipenv

Actual behavior

The status bar displays the current interpreter (the one in the venv created by pipenv) as Python 3.6.6 although the Python version is actually 3.5.4

image

Note that while the displayed version is wrong, everything else works correctly (i.e. linting and launching is performed with the selected interpreter, which is indeed 3.5.4 and not 3.6.6)

Expected behavior

The status bar and interpreter selector should display "Python 3.5.4 64-bit"

Steps to reproduce:

This was probably caused since I had a Python 3.6.6 venv in that same location before, so I'm guessing these steps will reproduce the issue but I'm not 100% sure.

  1. Create folder "test"
  2. Inside test run python3.6 -m pipenv install
  3. Open vscode to folder "test"
  4. Close vscode
  5. Run python3.6 -m pipenv --rm
  6. Run python3.5 -m pipenv install
  7. Open vscode to folder "test"

Logs

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

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help): https://pastebin.com/4xf0UWf4

@DonJayamanne
Copy link

Duplicate of #3406

@DonJayamanne DonJayamanne marked this as a duplicate of #3406 Dec 3, 2018
@syagev
Copy link
Author

syagev commented Dec 3, 2018

Crap. I actually read that issue and somehow didn't realize it's the same one.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants