{"id":7702,"date":"2020-05-12T09:47:09","date_gmt":"2020-05-12T17:47:09","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/python\/?p=7702"},"modified":"2020-06-03T10:52:42","modified_gmt":"2020-06-03T18:52:42","slug":"python-in-visual-studio-code-may-2020-release","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/python\/python-in-visual-studio-code-may-2020-release\/","title":{"rendered":"Python in Visual Studio Code \u2013 May 2020 Release"},"content":{"rendered":"

We are pleased to announce that the\u00a0<\/span>M<\/span>ay\u00a0<\/span>20<\/span>20<\/span>\u00a0<\/span>release of the Python Extension for Visual Studio Code is now available. You can<\/span> download the Python extension<\/span><\/a> from the Marketplace, or install it directly from the extension gallery in Visual Studio Code. If you already have the Python extension installed, you can also get the latest update by restarting Visual Studio Code. You can learn more about \u00a0<\/span>Python support in Visual Studio Code<\/span><\/a> in the documentation.\u00a0<\/span>\u00a0<\/span><\/p>\n

In this release we\u00a0<\/span>addressed<\/span>\u00a0<\/span>42<\/span>\u00a0<\/span>issues,<\/span>\u00a0<\/span>and it\u00a0<\/span>includ<\/span>es the<\/span>\u00a0<\/span>a<\/span>bility to\u00a0<\/span>browse\u00a0<\/span>for\u00a0<\/span>or\u00a0<\/span>enter an interpreter path on selection<\/span>.\u00a0<\/span>If you\u2019re interested, you can check the\u00a0<\/span>full list of improvements i<\/span>n\u00a0<\/span>our <\/span>changelog<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

Ability to\u00a0<\/span><\/span>browse<\/span><\/span>\u00a0<\/span><\/span>for\u00a0<\/span><\/span>interpreter path<\/span><\/span>\u00a0<\/span><\/span>\u00a0<\/span><\/h2>\n

To make selecting or changing interpreter easier, y<\/span><\/span>ou now\u00a0<\/span><\/span>have the option to browse\u00a0<\/span><\/span>for\u00a0<\/span><\/span>a Python interpreter in your file system<\/span><\/span>.\u00a0<\/span><\/span>Y<\/span><\/span>ou\u00a0<\/span><\/span>can<\/span><\/span>\u00a0also<\/span><\/span>\u00a0<\/span><\/span>s<\/span><\/span>et an interpreter by manually entering its path:<\/span><\/span><\/p>\n

\"Selecting<\/a>Theme: Eva<\/em><\/p>\n

Coming Next: moving python.pythonPath out of settings.json<\/span>\u00a0<\/span><\/h2>\n

One change that is <\/span>coming relates to how the Python extension handles Python interpreter selection. C<\/span>urrently the path to the selected interpreter\u00a0<\/span>is stored\u00a0<\/span>in the workspace settings. This can be a problem when you share VS Code workspace settings in a GitHub repo, for example, as\u00a0<\/span>reported in our issue tracker<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

In order to make the interpreter information system agnostic and prevent sharing the interpreter path (which commonly won\u2019t be the same across different machines), we\u2019re going to deprecate the\u00a0<\/span>python.pythonPath<\/em> setting in the Python extension.\u00a0 You will still be able to set interpreters per workspace, it’ll just be stored internally instead of the workspace settings.\u00a0<\/span><\/p>\n

These changes will be added gradually as an experiment.\u00a0<\/span>If you\u2019re interested to try it\u00a0<\/span>ahead of time, y<\/span>ou can opt into this functionality by adding the following line to your User settings (<\/span>View\u00a0<\/span><\/b>>\u00a0<\/span>Command Palette…\u00a0<\/span><\/b>and run\u00a0<\/span>Preferences: Open Settings (JSON)<\/span><\/b>) and then reloading the window (<\/span>View\u00a0<\/span><\/b>>\u00a0<\/span>Command Palette…<\/span><\/b>\u00a0and run\u00a0<\/span>Developer: Reload Window)<\/span><\/b>:<\/span>\u00a0<\/span><\/p>\n

\"python.experiments.optInto\":\u00a0[\"DeprecatePythonPath\u00a0- experiment\"]<\/pre>\n
To see if you are part of an experiment, you can check the first lines in the Python extension output channel. If you wish to opt-out of A\/B testing<\/span>\u00a0in general<\/span>, you can open the user\u00a0<\/span>settings.json<\/span>\u00a0file and set the “<\/span>python.experiments.enabled<\/span><\/i>” setting to\u00a0<\/span>false<\/span><\/i>.<\/span>\u00a0<\/span><\/p>\n
We also have some\u00a0<\/span>additional\u00a0<\/span>announcements coming soon, so stay tuned!<\/span>\u00a0<\/span><\/p>\n
Other Changes and Enhancements<\/span><\/span>\u00a0<\/span><\/h2>\n
We have also added small enhancements and fixed issues requested by users that should improve your experience working with Python in Visual Studio Code. Some notable changes include:<\/span>\u00a0<\/span><\/p>\n