{"id":7463,"date":"2019-10-08T13:58:05","date_gmt":"2019-10-08T21:58:05","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/python\/?p=7463"},"modified":"2020-06-03T10:53:08","modified_gmt":"2020-06-03T18:53:08","slug":"python-in-visual-studio-code-october-2019-release","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/python\/python-in-visual-studio-code-october-2019-release\/","title":{"rendered":"Python in Visual Studio Code \u2013 October 2019 Release"},"content":{"rendered":"

We are pleased to announce that the\u00a0<\/span>October\u00a0<\/span>2019 release of the Python Extension for Visual Studio Code is now available. You can\u202f<\/span>download the Python extension<\/a>\u202f<\/span>from the\u00a0Marketplace, or\u00a0install 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\u00a0about \u202f<\/span>Python support in Visual Studio Code <\/span><\/a>in the documentation.\u00a0<\/span>\u00a0<\/span><\/p>\n

In this release<\/span>\u00a0we\u00a0<\/span>addressed 97\u00a0<\/span>issues<\/span>,<\/span> including<\/span>\u00a0<\/span>native\u00a0<\/span>editing of\u00a0<\/span>Jupyter\u00a0<\/span>Notebooks<\/span>, a\u00a0<\/span>button<\/span>\u00a0<\/span>to run\u00a0<\/span>a\u00a0<\/span>Python file<\/span>\u00a0in the terminal<\/span>,<\/span>\u00a0<\/span>and\u00a0<\/span>linting and import improvements\u00a0with\u00a0<\/span>the Python Language Server<\/span>.<\/span>\u00a0<\/span>The full list of enhancements is listed in\u00a0<\/span>our<\/span>\u202f<\/span>changelog<\/span><\/a>.<\/span>\u00a0<\/span><\/p>\n

Native\u00a0<\/span>e<\/span>diting of\u00a0<\/span>Jupyter<\/span>\u00a0<\/span>Notebooks<\/span>\u00a0<\/span><\/h2>\n

We’re excited to announce the first release of<\/span>\u00a0native editing of<\/span>\u00a0Jupyter\u00a0notebook<\/span>s<\/span>\u00a0inside VS Code! The native\u00a0Jupyter\u00a0experience brings a<\/span>\u00a0new\u00a0<\/span>way for both data scientists and notebook developers alike to\u00a0<\/span>directly edit .ipynb\u00a0files and get the interactivity of\u00a0Jupyter\u00a0notebooks with all of the power of VS Code.\u00a0<\/span>You can check the <\/span>Native Support for Editing Jupyter Notebooks in VS Code<\/span><\/a> blog post to learn <\/span>more about this feature\u00a0<\/span>and how to get started<\/span>.<\/span><\/p>\n

\"\"<\/p>\n

Run Python File<\/span><\/span>\u00a0in\u00a0<\/span>Terminal<\/span><\/span>\u00a0button<\/span><\/span>\u00a0<\/span><\/h2>\n

This release\u00a0<\/span>includes a\u00a0<\/span>\u201c<\/span>play<\/span>\u201d\u00a0<\/span>button to\u00a0<\/span>run the\u00a0<\/span>Run Python File<\/span><\/b>\u00a0in Terminal<\/span><\/b>\u00a0<\/span><\/b>command.<\/span>\u00a0Now it only takes one click to run Python files with the Python extension!<\/span>\u00a0<\/span>\u00a0<\/span><\/p>\n

The new button is\u00a0<\/span>located on the top-right\u00a0<\/span>side of the editor,\u00a0<\/span>matching<\/span>\u00a0the\u00a0<\/span>behavior of the\u00a0<\/span>Code Runner<\/span><\/a>\u00a0extension<\/span>:<\/span>\u00a0<\/span><\/p>\n

\"\"<\/span><\/p>\n

\"\"<\/p>\n

I<\/span><\/span>f you’re<\/span><\/span>\u00a0<\/span><\/span>into\u00a0<\/span><\/span>key bindings, you can also\u00a0<\/span><\/span>customize your own\u00a0<\/span><\/span>keyboard\u00a0<\/span><\/span>shortcut<\/span><\/span><\/a>\u00a0to run Python files in the terminal<\/span><\/span>,<\/span><\/span>\u00a0by<\/span><\/span>\u00a0<\/span><\/span>run<\/span><\/span>ning<\/span><\/span>\u00a0<\/span><\/span>the <\/span><\/span>Preferences: Open Keyboard Shortcuts (JSON) <\/span><\/span><\/strong>command\u00a0<\/span><\/span>in the command palette (<\/span><\/span>View<\/strong>\u00a0<\/span><\/span>>\u00a0<\/span><\/span>Command Palette\u2026<\/span><\/span><\/strong>)<\/span><\/span>\u00a0and<\/span><\/span>\u00a0<\/span><\/span>enter<\/span><\/span>ing<\/span><\/span>\u00a0<\/span><\/span>a key binding for the\u00a0<\/span><\/span>python.execInTerminal<\/span>\u00a0<\/span><\/span>command\u00a0<\/span><\/span>as<\/span><\/span>\u00a0you<\/span><\/span>\u00a0<\/span><\/span>pr<\/span><\/span>efer<\/span><\/span>. For example, you could have the following\u00a0<\/span><\/span>definition\u00a0<\/span><\/span>to\u00a0<\/span><\/span>run Python<\/span><\/span>\u00a0file<\/span><\/span>s<\/span><\/span>\u00a0in the terminal with\u00a0<\/span><\/span>a custom shortcut:<\/span><\/span>\u00a0<\/span><\/p>\n

\"\"<\/p>\n

If the Code Runner extension is enabled, the Python extension doesn\u2019t display this button in order to avoid possible\u00a0<\/span><\/span>confusion<\/span><\/span>.<\/span><\/span>\u00a0<\/span><\/p>\n

Linting and import\u00a0<\/span><\/span>improvements\u00a0<\/span><\/span>with<\/span><\/span>\u00a0the Python Language Server<\/span><\/span>\u00a0<\/span><\/h2>\n

Additionally, there have been large improvements made to import resolution. Historically the Language Server has treated the workspace root as the\u00a0<\/span><\/span><\/span><\/span>sys.path<\/span><\/span><\/span><\/span>\u00a0entry (i.e.\u00a0<\/span><\/span><\/span><\/span>the\u00a0<\/span><\/span>main\u00a0<\/span><\/span><\/span><\/span>workspace\u00a0<\/span><\/span>root) of user module imports, which led to false-positive<\/span><\/span><\/span><\/span>\u00a0unresolved\u00a0<\/span><\/span><\/span><\/span>imports warnings when importing modules from a<\/span><\/span><\/span><\/span>\u00a0<\/span><\/span><\/span><\/span>src<\/span><\/span><\/span><\/span><\/em>\u00a0directory. With this release, if there\u2019s such a\u00a0<\/em><\/span><\/span><\/span><\/span>src<\/span><\/span><\/span><\/span><\/em>\u00a0<\/span><\/span><\/span><\/span>directory in the project\u2019s environment, the Language Server automatically detects and adds\u00a0<\/span><\/span><\/span><\/span>the<\/span><\/span>\u00a0<\/span><\/span><\/span><\/span>directory to its\u00a0<\/span><\/span><\/span><\/span>list of\u00a0<\/span><\/span>search path<\/span><\/span><\/span><\/span>s<\/span><\/span>. You can refer to the\u00a0<\/span><\/span><\/span><\/span>documentation<\/span><\/span><\/span><\/span><\/a>\u00a0<\/span><\/span><\/span><\/span>to learn more about\u00a0<\/span><\/span><\/span><\/span>configuring<\/span><\/span>\u00a0search paths\u00a0<\/span><\/span><\/span><\/span>for\u00a0<\/span><\/span>the Language Server.<\/span><\/span><\/span><\/span>\u00a0<\/span><\/p>\n

Other Changes and Enhancements<\/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

This release also includes<\/span><\/span>\u00a0<\/span><\/span>three\u00a0<\/span><\/span>new linting rules<\/span><\/span><\/a>\u00a0with the Python Language Server, as well as<\/span><\/span>\u00a0significant improvements to autocompletion for packages such as\u00a0<\/span><\/span>PyTorch<\/span><\/span>\u00a0and pandas<\/span><\/span>.<\/span><\/span><\/span><\/p>\n