3 ms·
>I have converted to VSCode because it just works and I don't have to mess with PATH or whatever. While I love VSCode and use it every day (mostly for markdown
by ImaCake 6y ago
>I have converted to VSCode because it just works and I don't have to mess with PATH or whatever.
While I love VSCode and use it every day (mostly for markdown), I have definitely needed to play around with PATHs to get VSCode working nicely with my conda installs on both windows and mac (i.e. it never seems to actually point to the right python interpreter). No idea who is at fault here, but it seems to be a consistent problem for me.
- int_19h 6y agoThe problems with Conda usually have to do with its activation. If you manually activate whatever environment you want before starting VSCode, it should pick it up fine. But if you don't, and then later you pick a conda environment, it'll try to auto-activate it in the terminal for you - and this part is brittle, because anything else using the terminal can interfere with it (and vice versa).
- ImaCake 6y agoYep I think you are right. It does seem to be when VScode tries to auto activate it. This github issue had a solution in the form of adding an empty string for a particular option in settings.json [0]. This fixed it for my mac install. I can't remember what I did on windows to fix it. 0. https://github.com/microsoft/vscode-python/issues/4434 https://github.com/microsoft/vscode-python/issues/4434