It is a Plone project with some files that kick the javascript VS code extension to 100% cpu utilization without doing anything. I found out about this separate configuration storage last week when I wanted to disable the MS javascript/typescript extension for my workspace. Personally I find this very vague and get windows registry deja vu's. It remembers for which Workspace you set the interpreter this. Until I started setting pythonPath explicitly in my settings.json, VS Code would refuse to pick up my venv/virtualenv inside the workspaceFolder, no matter which instructions I followed from their documentation.Ī separate issue but related is that you can still 'set' the default interpreter for your workspace using a shortcut/preference window, but the setting is stored in an internal VS Code config storage only accessible through an API.
Beats me why you have to remove the option alltogether for everybody else. What I've read in the proposal/docs so far is, because some teams using Python don't isolate their python installs and hence a Python install can be anywhere on their developer machines, setting a pythonPath explictly breaks those setups and detection should be done 'automatically'. In the npm/yarn world I kind of accept this as the packaging system there has has a strong local/global distinction from the start and an isolated project starts from where package.json is found in the directory tree. This is very similar to what nvm (node version manager) is doing for node/javascript. Some other tools/wrappers around venv (virtualenvwrapper) kind of manage virtualenv installed in a central location, presumably under your user/home folder and the wrapper activated the correct venv for your project, but you share venvs between multiple projects. So 1 virtualenv per project, inside the project. It completely breaks setting up reproducable environments automated.Īt Zest we have set up our Plone projects to be as reproducable as possible, so we install a virtualenv in all our project folders for proper isolation of Python modules. Here's another alternative answer, I think more accurate.Īdd following settings to your vscode user settings file: "code-runner.I haven't read everything yet, but don't understand why they have opted to remove the complete pythonPath parameter.
0 kommentar(er)
