The Python in VS Code team breaks a large extension – Visual Studio Magazine



Python in the VS Code team breaks a large extension

Microsoft’s Python in Visual Studio Code development team began splitting its super-popular big extension into separate tools in the regular April 2022 monthly update.

The team manages the Python extension in the VS Code marketplace, providing IntelliSense, linting, debugging, and more. It is by far the most popular tool on the market with over 53 million installs, almost 20 million more than any other extension.

In the April 2022 release, the team announced the first expansion to be split from the main expansion, Pylint.

“Our team is working to split support for the tools we offer in the Python extension into separate extensions, with the goal of improving performance, stability, and no longer requiring the tools to be installed in an environment Python – because they can come with an extension,” said Karthik Nadig. “The first one we started working on is Pylint.

As its name suggests, the tool provides linting functionality, the highlighting of syntactic and stylistic issues in Python source code to help coders identify and fix subtle programming errors or possibly bad practices. error-prone unconventional coding.

Pylint in action
[Click on image for larger, animated GIF view.] Pylint in action (source: Microsoft).

It’s unclear exactly how many of these tools are bundled into the main Python extension or how many will be separated, but the documentation shows that Pylint is among the various projects the tool is integrated into:

  • Debugging support: Django, Flask, gevent, Jinja, Pyramid, PySpark, Scrapy, Watson
  • Layout: autopep8, black, yapf
  • Interpreter assistance: conda, direnv, pipenv, poetry, pyenv, venv, virtualenv
  • Fluff: bandit, flake8, mypy, prospector, pylint, pydocstyle, pylama
  • Test: pytest, unit test

Other highlights of the latest update include:

  • Display of the interpreter in the status bar moved to the right: The display of the selected interpreter version has been moved to the right in the status bar, next to the Python language status item. To avoid cluttering the status bar, it only appears when a Python or settings.json file is open.
  • An easier way to create empty Python and Jupyter Notebook files: Developers can use the “File: Create New…” command in the command palette to create empty Python or Jupyter notebook files. The same functionality comes by clicking “New File…” from the VS Code home page.
  • Fix for running and debugging files with Conda environments: Fixed issues that caused regression when running files in conda enabled environments.

About the Author

David Ramel is an editor and writer for Converge360.


Comments are closed.