-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Changes to logic for selection of best (default) version of Python interpreter #3813
Conversation
9e6975a
to
2bc224e
Compare
* master: Added system tests to check activation for virtual environments (#3592)
7ea2c32
to
3b56b15
Compare
* master: Improvements to message displayed when linter is not installed (#3798)
Overall I like the change. There will have to be some back and forth on what constitutes the 'best interpreter' but I think you've largely nailed it for the majority of our users. I like the approach you took with the rule evaluator, I think that will make it very simple/flexible to sort out issues or change priority of 'best interpreters' found on a system. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still a few comments. |
For #3369
Depends on #3809
Depends on #3812
Add tests for
configSettings.ts
by injectingIWorkspaceService
.This must be done as Multi Root (functional) tests failed.
We need to add unit tests to cover it.
Add tests (Would be nice to see convertPythonVersionToSemver get some unit test attention. Otherwise, this PR looks great. I do appreciate the large amount of work it took to replace this functionality with SemVer!)
package-lock.json
has been regenerated by runningnpm install
(if dependencies have changed)