Python in Visual Studio Code – November 2019 Release

Luciana Abud

We are pleased to announce that the November 2019 release of the Python Extension for Visual Studio Code is now available. You can  download the Python extension 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  Python support in Visual Studio Code  in the documentation.  

In this release we focused mostly on product quality. We closed a total of 60 issues, 39 of them being bug fixes. However, we’re also pleased to deliver delightful features such as: 

  • Add imports “quick fix” when using the Python Language Server 
  • Altair plot support  
  • Line numbers in the Notebook Editor 

If you’re interested, you can check the full list of improvements iour changelog. 

Add Imports “Quick Fix” when using the Python Language Server 

We’re excited to announce that we have brought the magic of automatic imports to Python developers in VS Code by way of an add imports quick fix. Automatic imports functionality was one of the most requested features on our GitHub repo (GH21), and when you enable the Microsoft Language Server, you will get this new functionality. To enable the Language Server, add the setting python.jediEnabled: false to your settings.json file. 

The add imports quick fix within VS Code is triggered via code action lightbulb. To use the quick fix, begin typing a package name within the editor for which you do not have an import statement at the header of the file. You will notice that if a code action is available for this package (i.e. you have a module installed within your environment with the name you’ve supplied), a yellow squiggle will appear. If you hover over that text, code action lightbulb will appear indicating that an ’import code action is available for the package. You’ll see a list of potential imports (again, based on what’s installed within your environment), allowing you to choose the package that you wish to import. 

Example of auto import suggestion for path submodule

The add imports code action will also recognize some of the most popular abbreviations for the following Python packages: numpy as nptensorflow as tf, pandas as pdmatplotlib.pyplot as plt, matplotlib as mpl, math as m, as spio, and scipy as sp. 

Example of auto completions suggestions behaviour

The import suggestion list is ordered such that all import statements that appear at the top of the list are package (or module) imports; those that appear lower in the list are import statements for additional modules and/or members (e.g. classes, objects, etc.) from specified packages. 

Import suggestion for sys module

Make sure you have linting enabled since this functionality is tied to the Language Server linting capability. You can enable linting by opening the Command Palette (View > Command Palette…), running the “Python: Enable Linting” command and selecting “On” in the drop-down menu. 

Altair plots support

The Notebook Editor and the Python Interactive window now both support rendering plots built with Altair,  a declarative statistical visualization library for Python.

Jupyter Notebook example displaying Altair support

Line Numbers in the Notebook Editor

Line numbers are now supported in the notebook editor. On selected code cells, you can toggle the line numbers by pressing the “L” key.

Other Changes and Enhancements

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:

  • Fix running a unittest file to not execute only the first test. (thanks Nikolay Kondratyev). (#4567)
  • Added commands translation for Farsi and Turkish (thanks Nikronic). (#8092)
  • Added command translations for Turkish (thanks alioguzhan). (#8320)
  • Place all plots on a white background regardless of theme. (#8000)

We are continuing to A/B test new features, so if you see something different that was not announced by the team, you may be part of the experiment! 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, you can open the user settings.json file (View > Command Palette… and run Preferences: Open Settings (JSON)) and set the “python.experiments.enabled” setting to false.

Be sure to download the Python extension for Visual Studio Code now to try out the above improvements. If you run into any problems, please file an issue on the Python VS Code GitHub page.


Discussion is closed. Login to edit/delete existing comments.

  • Kenneth Sherwood Munk 0

    Yes, finally. I’ve been waiting for something like this so that I can consolidate my tooling.

  • Alex Pintea 0

    Thank you for these great news!

Feedback usabilla icon