HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
microsoft
vscode-python
TypeScript2017–2025
microsoft / vscode-python

vscode-python

Python extension for Visual Studio Code

23Distinct people
31Mentions
0Explicit recommenders
4.7KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Python extension for Visual Studio Code

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year31 dated mentions

Observed mentions: 2017-11-14 19:34:20 UTC to 2025-03-30 15:44:11 UTC.

0369122017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC101
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC11011
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC707
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC505
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC303
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC202
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Python extension for Visual Studio Code A Visual Studio Code extension with rich support for the Python language (for all actively supported Python versions), providing access points for extensions to seamlessly integrate and offer support for IntelliSense (Pylance), debugging (Python Debugger), formatting, linting, code navigation, refactoring, variable explorer, test explorer, environment management (NEW Python Environments Extension). Support for vscode.dev The Python extension does offer some support when running on vscode.dev (which includes github.dev). This includes partial IntelliSense for open files in the editor. Installed extensions The Python extension will automatically install the following extensions by default to provide the best Python development experience in VS Code: Pylance – performant Python language support Python Debugger – seamless debug experience with debugpy (NEW) Python Environments – dedicated environment management (see below) These extensions are optional dependencies, meaning the Python extension will remain fully functional if they fail to be installed. Any or all of these extensions can be disabled or uninstalled at the expense of some features. Extensions installed through the marketplace are subject to the Marketplace Terms of Use. About the Python Environments Extension You may now see that the Python Environments Extension is installed for you, but it may or may not be "enabled" in your VS Code experience. Enablement is controlled by the setting "python.useEnvironmentsExtension": true (or false). If you set this setting to true, you will manually opt in to using the Python Environments Extension for environment management. If you do not have this setting specified, you may be randomly assigned to have it turned on as we roll it out until it becomes the default experience for all users. The Python Environments Extension is still under active development and experimentation. Its goal is to provide a dedicated view and improved workflows for creating, deleting, and switching between Python environments, as well as managing packages. If you have feedback, please let us know via issues. Extensibility The Python extension provides pluggable access points for extensions that extend various feature areas to further improve your Python development experience. These extensions are all optional and depend on your project configuration and preferences. Python formatters Python linters If you encounter issues with any of the listed extensions, please file an issue in its corresponding repo. Quick start Step 1. Install a supported version of Python on your system (note: the system install of Python on macOS is not supported). Step 2. Install the Python extension for Visual Studio Code. Step 3. Open or create a Python file and start coding! Set up your environment Select your Python interpreter by clicking on the status bar Configure the debugger through the Debug Activity Bar Configure tests by running the Configure Tests command Jupyter Notebook quick start The Python extension offers support for Jupyter notebooks via the Jupyter extension to provide you a great Python notebook experience in VS Code. Install the Jupyter extension. Open or create a Jupyter Notebook file (.ipynb) and start coding in our Notebook Editor! For more information you can: Follow our Python tutorial with step-by-step instructions for building a simple app. Check out the Python documentation on the VS Code site for general information about using the extension. Check out the Jupyter Notebook documentation on the VS Code site for information about using Jupyter Notebooks in VS Code. Useful commands Open the Command Palette (Command+Shift+P on macOS and Ctrl+Shift+P on Windows/Linux) and type in one of the following commands: Command Description Python: Select Interpreter Switch between Python interpreters, versions, and environments. Python: Start Terminal REPL Start an interactive Python REPL using the selected interpreter in the VS Code terminal. Python: Run Python File in Terminal Runs the active Python file in the VS Code terminal. You can also run a Python file by right-clicking on the file and selecting Run Python File in Terminal. Python: Configure Tests Select a test framework and configure it to display the Test Explorer. To see all available Python commands, open the Command Palette and type Python. For Jupyter extension commands, just type Jupyter. Feature details Learn more about the rich features of the Python extension: IntelliSense: Edit your code with auto-completion, code navigation, syntax checking and more. Linting: Get additional code analysis with Pylint, Flake8 and more. Code formatting: Format your code with black, autopep or yapf. Debugging: Debug your Python scripts, web apps, remote or multi-threaded processes. Testing: Run and debug tests through the Test Explorer with unittest or pytest. Jupyter Notebooks: Create and edit Jupyter Notebooks, add and run code cells, render plots, visualize variables through the variable explorer, visualize dataframes with the data viewer, and more. Environments: Automatically activate and switch between virtualenv, venv, pipenv, conda and pyenv environments. Refactoring: Restructure your Python code with variable extraction and method extraction. Additionally, there is componentized support to enable additional refactoring, such as import sorting, through extensions including isort and Ruff. Supported locales The extension is available in multiple languages: de, en, es, fa, fr, it, ja, ko-kr, nl, pl, pt-br, ru, tr, zh-cn, zh-tw Questions, issues, feature requests, and contributions If you have a question about how to accomplish something with the extension, please ask on our Discussions page. If you come across a problem with the extension, please file an issue. Contributions are always welcome! Please see our contributing guide for more details. Any and all feedback is apprecia
Read the full README on GitHub

What Hacker News says

11 sources
Hey great to hear the excitement for this. In fact, we (the Python VSCode extension team) were so excited about it, that we've already begun integrating it into the python VSCode extension itself! It's a little rough yet for a full release but it's highly functional. If you want to play with it, just build the extension from https://github.com/Microsoft/vscode-python. Suggestions are welcome, but remember, it's still undergoing changes.
In Neuron, a new VS Code extension for data science
I'm on the same boat, since I only use pyenv inside WSL. It's something that is being discussed (and worked on for other languages). The relevant issue is at: - https://github.com/Microsoft/vscode-python/issues/67 And the VS Code team was asking for folk to interview regarding WSL integration: https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGG... (Full disclosure: I work at Microsoft, but in other teams, and am eagerly waiting for the day I can use WSL pyenvs)
In Python in Visual Studio Code
Never thought that code editor from the MSFT would become my daily driver IDE. The only feature I need most from the VSCode (which is not implemented yet) is Python Remote interpreter[1]. While `ptvsd` is more or less convenient for remote debugging, it doesn't help when you need IntelliSense/linting while developing code being interpreted in container/virtual machine/remote host. IntelliJ PyCharm is clearly ahead here for now. [1] Issue #79: https://github.com/Microsoft/vscode-python/issues/79
In Python in Visual Studio Code
We've got about 30+ backends in python all wrapped in docker containers. Majority of the team was pure vim before I joined and they're slowly converting to pycharm after seeing how nicely you can setup a remote interpreter against a docker container. And it has vim bindings so you don't have to re-learn new hotkeys. I've also been following this VS Code issue on adding remote docker support for python https://github.com/Microsoft/vscode-python/issues/79#issueco... However, if you're a hardcore vim guy then I doubt these IDEs are gonna satiate your current flow.
In My Python Development Environment, 2018 Edition

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.