-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Log and ignore errors when looking for interpreters #293
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
Log and ignore errors when looking for interpreters #293
Conversation
Archive of 0.7.0
* 'master' of https://github.com/Microsoft/vscode-python: Fixes #56 list all environments (#219) Fixes #57 Disable activation on debugging (#220) Fixes #26 Do not run linters when linters are disabled (#222)
* upstream/master: Fix typo in README.md (#252) Disable linter without workspaces (#241)
* upstream/master: Fix feedback service (#246) Fix django context initializer (#248) disable generation of tags file upon extension load (#264)
* upstream/master: Resolve pythonPath before comparing it to shebang (#273)
* upstream/master:
Fixes #22 to Detect anaconda from known locations (#221)
Use workspaceFolder token instead of workspaceRoot (#267)
Fix registry lookup response (#224)
Fix issues when running without debugging and debugged code terminates (#249)
|
Restarted the tests, nothing has changed. No idea why python tools don't work reliably. Once the execution engine is done, i'll inject the stdout in the unit tests via a mock python tool runner & have separate test to ensure running of python tools work as expected (including parsing of the responses, etc). |
Fixes #276 by adding exception handling when looking for interpreters. Exceptions are logged and ignored.
Also made use of path.normalize instead of doing it manually (reduced some linter rules as they are unnecessarily strict)