Log interpreter search info to the Output window

Environment data

VS Code version: Version 1.18.0 (1.18.0) Python Extension version: 0.8.0 Python Version: multiple OS and version: MacOS 10.13.1

Something changed recently where the first time I open a Python project I’ll see a bunch of crash notifications from the system crash reporter for many versions of Python. It looks like what’s happening is that VSCode is now trying to index every Python executable in a virtualenv (which I have a fair number of thanks to tools like tox) and anything which is old enough that the Homebrew Python version has changed were crashing when the dynamic linker tried to load a shared library version which was no longer installed.

It seems a little wasteful of I/O to crawl the user’s home directory so aggressively — my projects had pythonPath set — but it’s probably friendlier in general. Since there’s no output in the error log, debug terminal, or console window, however, it seems like it’d be at least helpful to log a message that an executable crashed on startup.

Logs

Output from Python output panel

----------Generating Tags----------
ctags --options=/Users/cadams/.vscode/extensions/ms-python.python-0.8.0/resources/ctagOptions --languages=Python --exclude=**/site-packages/** -o /Users/cadams/Projects/bagit-python/.vscode/tags .
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ctags: illegal option -- -
usage: ctags [-BFadtuwvx] [-f tagsfile] file ...
##########Linting Output - flake8##########
33,1,E,E303:too many blank lines (3)
774,9,E,E722:do not use bare except'
1296,16,F,F821:undefined name 'unicode'

Output from Console window (Help->Developer Tools menu)

console.ts:123 [Extension Host] (node:12495) DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
t.log @ console.ts:123
t._logExtensionHostMessage @ extensionHost.ts:377
(anonymous) @ extensionHost.ts:202
emitTwo @ events.js:106
emit @ events.js:194
process.nextTick @ internal/child_process.js:766
_combinedTickCallback @ internal/process/next_tick.js:73
_tickCallback @ internal/process/next_tick.js:104

[brettcannon]

Adding this to our “lower support costs” project as we should be logging this sort of stuff to help in debugging issues for users.

[brettcannon]

We are now emitting to the Output Panel all of the executions of Python that we do, so hopefully this meets your needs, @acdha . If it doesn’t then we can reopen and chat about what is still lacking.