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.

Sign up for GitHub

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

Jump to bottom

Interpreter information displayed in status bar is incorrect #981

Closed
DonJayamanne opened this issue Mar 7, 2018 · 0 comments · Fixed by #1054
Closed

Interpreter information displayed in status bar is incorrect #981

DonJayamanne opened this issue Mar 7, 2018 · 0 comments · Fixed by #1054
Assignees
@DonJayamanne
Labels
bug Issue identified by VS Code Team member as probable bug
Milestone
March 2018

Comments

@DonJayamanne
Copy link

  • OS - Windows
  • Create a workspace
  • Create a virtual environment
  • Open a python file
  • For a brief second the status bar will display interperter x and then switch over to the virtual env created.

Problem: When extension loads we're manually firing off the change event, and when interpreter gets auto-selected, another change event gets fired.
@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug needs PR labels Mar 7, 2018
@DonJayamanne DonJayamanne added this to the March 2018 milestone Mar 7, 2018
@DonJayamanne DonJayamanne self-assigned this Mar 7, 2018
@DonJayamanne DonJayamanne mentioned this issue Mar 13, 2018
Merged
DonJayamanne added a commit that referenced this issue Mar 15, 2018
@DonJayamanne
Fixes issue that display incorrect interpreter briefly before updatin…
822cd7a 
…g it to the right value (#1054)

* 🐛 fire change event only when changes are detected
* 📝 change log
* 🔨 fix typos
* Fixes #981
@lock lock bot locked as resolved and limited conversation to collaborators Jul 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@DonJayamanne DonJayamanne

Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Milestone
March 2018
2 participants
@brettcannon @DonJayamanne