-
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
Python Language Server "unable to determine path to interpreter" should be actionable #2983
Comments
Fix for microsoft#2983 - Add button to warning message that opens interpreter selector - Add localization
Current behaviour is indeed unactionable: I propose we do something like so: Branch for person who would implement such a thing. Note: The popup for dependencies such as linters should probably be deferred until after this action is taken as well. Covered in #2811. |
@d3r3kk
Benefits:
|
Changing label to |
@brettcannon |
…ly selected, make the message actionalble. For microsoft#2983 - [x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR) - [x] Title summarizes what is changing - [x] Has a [news entry](https://github.com/Microsoft/vscode-python/tree/master/news) file (remember to thank yourself!) - [x] Unit tests & system/integration tests are added/updated - [x] ~[Test plan](https://github.com/Microsoft/vscode-python/blob/master/.github/test_plan.md) is updated as appropriate~ *(This is covered by assertions already present)* - [x] ~[`package-lock.json`](https://github.com/Microsoft/vscode-python/blob/master/package-lock.json) has been regenerated by running `npm install` (if dependencies have changed)~
Environment data
Actual behavior
Opened a folder with a single empty hello.py file:
![image](https://user-images.githubusercontent.com/17804393/47328150-c493fe00-d624-11e8-885d-780e947b32b0.png)
No python interpreter is selected, and I get this error message immediately after opening the file
Expected behavior
The dialog should instead say something like
The text was updated successfully, but these errors were encountered: