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 list reporting global interpreters twice & reporting wrong bugfix version #3953

Closed
brettcannon opened this issue Jan 10, 2019 · 1 comment
Closed

Interpreter list reporting global interpreters twice & reporting wrong bugfix version #3953

brettcannon opened this issue Jan 10, 2019 · 1 comment
Assignees
@DonJayamanne
Labels
bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority
Milestone
2019, week 3 - Ja...

Comments

@brettcannon
Copy link
Member

image
None of those interpreters are at a .0 bugfix release.
@ghost ghost added the triage-needed Needs assignment to the proper sub-team label Jan 10, 2019
@DonJayamanne DonJayamanne self-assigned this Jan 10, 2019
@DonJayamanne DonJayamanne added bug Issue identified by VS Code Team member as probable bug needs PR labels Jan 10, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Jan 10, 2019
@DonJayamanne
Copy link

I came across this bug when testing PR #3330
It's is being addressed there.
The problem is simple, the version info stored in registry is not the same as that returned by python, the patch isn't stored in the registry.

@DonJayamanne DonJayamanne mentioned this issue Jan 10, 2019
Merged
6 tasks
@qubitron qubitron added the important Issue identified as high-priority label Jan 16, 2019
@d3r3kk d3r3kk added this to the 2019, week 3 - Jan Sprint 2 milestone Jan 17, 2019
@ghost ghost removed the needs PR label Jan 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Feb 25, 2019
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 important Issue identified as high-priority
Projects
None yet
Milestone
2019, week 3 - Jan Sprint 2
Development

No branches or pull requests
5 participants
@brettcannon @DonJayamanne @d3r3kk @karrtikr @qubitron