1 Release published by 1 person

• v2025.6.1

  published May 15, 2025

30 Pull requests merged by 7 people

• bump to 2025.9

  #25149 merged Jun 5, 2025

• Bump to 2025.8.0

  #25148 merged Jun 5, 2025

• Bump tar-fs from 2.1.2 to 2.1.3

  #25138 merged Jun 4, 2025

• Ensure we do not support the tools in an untrusted workspace

  #25142 merged Jun 4, 2025

• All Python lm tools in Python extension

  #25116 merged May 29, 2025

• Update lm tool tags

  #25114 merged May 28, 2025

• Update tool args

  #25113 merged May 28, 2025

• Support additional args for create venv tool

  #25112 merged May 27, 2025

• Update lm tool tags

  #25108 merged May 27, 2025

• Configuration tool with improved workflow and UX

  #25106 merged May 27, 2025

• Remove single quotes surrounding displayed venv

  #25102 merged May 23, 2025

• Add activation events for tools

  #25104 merged May 23, 2025

• Prefer using Notebook tools over Python tools for notebooks

  #25098 merged May 21, 2025

• fix: ensure we always return undefined for invalid envs

  #25092 merged May 20, 2025

• Configure Python Env tool

  #25091 merged May 20, 2025

• Ability to track the user selected Environment

  #25090 merged May 20, 2025

• Ensure python selector supports returning created env

  #25088 merged May 19, 2025

• Tweak Python shell integration for lsp completion

  #25082 merged May 17, 2025

• API to get last used env in a LM tool

  #25079 merged May 16, 2025

• More specific llm tools

  #25072 merged May 16, 2025

• Rename llm tools

  #25078 merged May 15, 2025

• bump release 2025.6.1

  #25077 merged May 15, 2025

• chore: ensure .env files are excluded from vsix

  #25075 merged May 15, 2025

• chore: ensure .env files are excluded from vsix

  #25076 merged May 15, 2025

• fix regression with import packaging for branch coverage (#25070)

  #25074 merged May 15, 2025

• fix regression with import packaging for branch coverage

  #25070 merged May 15, 2025

• Port Python Env Tools

  #25066 merged May 14, 2025

• Updates to latest version of VS Code types

  #25065 merged May 13, 2025

• Fix msys2 venv path

  #25062 merged May 13, 2025

• Fix env error handling

  #25049 merged May 12, 2025

8 Pull requests opened by 3 people

• Handle cases when failing to resolve env

  #25095 opened May 20, 2025

• Add some verbose logging

  #25096 opened May 20, 2025

• Add telemetry for when user triggers testing from CLI

  #25103 opened May 23, 2025

• Allow Activated Virtual Envs to Be Detected w/ a Workspace File

  #25141 opened Jun 3, 2025

• Account for editor.multiCursorModifier setting in Native REPL terminal link

  #25156 opened Jun 10, 2025

• Fix Python >= 3.13 terminal execution requiring manual Enter keypresses

  #25157 opened Jun 10, 2025

• Add option to reuse existing Python terminals for code execution

  #25158 opened Jun 10, 2025

• Fix "Run Python File" executing in Python REPL instead of shell

  #25160 opened Jun 10, 2025

32 Issues closed by 11 people

• After installing Python from Windows store, kernel selector shows version as undefined

  #25165 closed Jun 12, 2025

• Sugerencia: Mejorar gestión de historial de chat (eliminar no fijados, selección múltiple

  #25162 closed Jun 10, 2025

• Non-stop reactivating terminal

  #25155 closed Jun 10, 2025

• Release Plan v2025.6.0

  #25032 closed Jun 5, 2025

• TPI: Exploratory Python Envs

  #25135 closed Jun 2, 2025

• Test output is not kept for sucessful tests (pytest)

  #25111 closed Jun 2, 2025

• Missing Quotes for Python Path Argument - Space in Python Path Prevents Debugging with Arguments

  #25119 closed Jun 2, 2025

• Python

  #25132 closed May 31, 2025

• [error] Unable to find workspace for given file

  #25101 closed May 29, 2025

• getActiveInterpreter Does Not Return User-Selected Interpreter When Stored in Workspace Storage

  #25109 closed May 29, 2025

• hata var

  #25110 closed May 27, 2025

• Test provider types are not aligned

  #24926 closed May 27, 2025

• paths, variables, and go talk to someone else

  #25100 closed May 27, 2025

• jupyter.kernels.excludePythonEnvironments is ignored

  #25107 closed May 25, 2025

• Remove quotes from environment name in the status bar and interpreter selector

  #23978 closed May 23, 2025

• Pylance Fails to Resolve Import from venv; Python Extension Uses Global Python for Helper Scripts

  #25099 closed May 22, 2025

• Implement Python terminal completion provider

  #24776 closed May 21, 2025

• Cached Python Environments not cleared when deleting an env

  #25087 closed May 20, 2025

• Add command for `getDebuggerPackagePath`

  #25081 closed May 19, 2025

• Python extension loads the env var incorrectly

  #24575 closed May 18, 2025

• nothing interesting

  #25084 closed May 18, 2025

• Tweak Python terminal shell integration for lsp completion

  #25012 closed May 17, 2025

• Wrong python selected after select interpreter

  #25061 closed May 15, 2025

• "ModuleNotFoundError: No module named 'packaging'" occurs when running unit tests

  #25044 closed May 15, 2025

• Exposed API updateActiveEnvironmentPath outside workspace

  #25045 closed May 14, 2025

• Incorrect PATH after selecting interpreter

  #25048 closed May 14, 2025

• Having pygls.protocol.json_rpc ValueError after updating to 2025.6.0 from 2025.4.0

  #25060 closed May 14, 2025

• MSYS2 (MinGW32/64 or UCRT64) fails on Create virtual environment .venv

  #24792 closed May 13, 2025

• The anaconda environment is not activated automatically when I open the terminal. Although I can see the environment name in terminal, it is not actually activated. The `which python` command output the base env of the anaconda.

  #25052 closed May 12, 2025

• A failure to find an environment prevents Pylance from loading

  #24211 closed May 12, 2025

• BiruleibinhoTest

  #25055 closed May 12, 2025

• Stuck on Reactivating Terminals

  #25053 closed May 12, 2025

27 Issues opened by 24 people

• Disable PyREPL for > 3.13

  #25164 opened Jun 11, 2025

• Pixi shell auto-activation can't be disabled

  #25163 opened Jun 11, 2025

• Status bar shows wrong Python version for selected virtual environment

  #25161 opened Jun 10, 2025

• legacy setup.py -> PyTorch

  #25154 opened Jun 9, 2025

• My issues: it still shows no flask module even after activating venv and installing flask and after flask run still shows the module not installed. Below is my problem:

  #25153 opened Jun 9, 2025

• Support for the use and rendering of LaTeX in tooltips

  #25152 opened Jun 9, 2025

• Invalid Python env selected error message displayed just before another message that env was selected

  #25150 opened Jun 6, 2025

• Release Plan v.2025.8.0

  #25147 opened Jun 5, 2025

• Hide progress messages when invoking tools

  #25143 opened Jun 4, 2025

• Activated VirtualEnvs Are Ignored When Launching from CLI with Workspace File

  #25140 opened Jun 3, 2025

• VScode complains about being unable to find virtual python environment

  #25139 opened Jun 3, 2025

• Failed to resolve env. An unknown error occurred

  #25137 opened Jun 3, 2025

• Vscode doesn't know which Python virtualenv to use if there there are multiple python projects opened

  #25134 opened Jun 1, 2025

• Hangs at Discovering Python Interpreters

  #25120 opened May 30, 2025

• Using smart send with REPL leads to NameError for every line of code

  #25117 opened May 29, 2025

• VS Code cannot cancel test

  #25115 opened May 28, 2025

• Terminal Environment Contributions: Path Modifications get Overwritten

  #25097 opened May 21, 2025

• Python, Python Debugger, and Pylance extensions fail to activate inside Dev Container after rebuilding

  #25094 opened May 20, 2025

• Coverage ignores report options

  #25086 opened May 19, 2025

• Feature Request: dependencies syntax highlighting for `pyproject.toml` files

  #25080 opened May 16, 2025

• Hide progress messages when invoking tools

  #25073 opened May 15, 2025

• Support pytest test discovery in monorepo setup with multipe tests/conftest.py

  #25069 opened May 14, 2025

• Selecting a uv `.venv/bin/python` as active interpreter doesn't enable IDE feature

  #25068 opened May 14, 2025

• Integrated Terminal in Insiders Fails to Activate Selected Python Environment which is 3.12.10 (Falls back to System Default 3.11.12)

  #25067 opened May 14, 2025

• Do not fail test discovery on failure

  #25058 opened May 13, 2025

• Kernel picker wrongly displays `Python 2.7.undefined` for a valid `Python 3.12` kernel

  #25146 opened May 12, 2025

• Unable to run Django tests via Sidebar

  #25056 opened May 12, 2025

57 Unresolved conversations

Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.

• Implement copying python import path from opened file

  #25026 commented on May 23, 2025 • 13 new comments

• set python.terminal.executeInFileDir not working, python file run earlier than cd command

  #25024 commented on May 13, 2025 • 0 new comments

• Change venvFolders to no longer be anchored to the user's home directory

  #1479 commented on May 26, 2025 • 0 new comments

• Missing brackts around virtual environment name in command prompt

  #24917 commented on May 26, 2025 • 0 new comments

• Actived Python Environment only partially works

  #25036 commented on May 27, 2025 • 0 new comments

• Please change default tests coverage argument to `--cov` or allow users to configure it

  #24973 commented on May 27, 2025 • 0 new comments

• Django test discovering

  #24991 commented on May 27, 2025 • 0 new comments

• Add short title to "Run Selection/Line in Python Terminal" command

  #22008 commented on May 27, 2025 • 0 new comments

• Test discovery fails

  #24978 commented on May 29, 2025 • 0 new comments

• Add filter based on pytest marks to Test Explorer

  #20350 commented on May 29, 2025 • 0 new comments

• Multi-root workspace: Python resolves imports only from venv of first root-folder

  #23448 commented on May 30, 2025 • 0 new comments

• Fix environment-dependent git pre-commit hooks

  #10165 commented on May 30, 2025 • 0 new comments

• Add telemetry for when user triggers testing from CLI

  #24562 commented on Jun 3, 2025 • 0 new comments

• Globally disable installing `pytest` if missing

  #24727 commented on Jun 3, 2025 • 0 new comments

• Make sure there's no await between clearing and filling the environment

  #24914 commented on Jun 3, 2025 • 0 new comments

• Local imports do not work in native REPL - sys.path differs from cwd than expected

  #24361 commented on Jun 3, 2025 • 0 new comments

• venv cannot be select in jupyter

  #25144 commented on Jun 4, 2025 • 0 new comments

• Get python for users with no python installed

  #24963 commented on Jun 5, 2025 • 0 new comments

• `uv` in python dev containers

  #24961 commented on Jun 5, 2025 • 0 new comments

• Terminal does not activate my ".conda" environment that is selected as "Current Interpreter"

  #24472 commented on Jun 5, 2025 • 0 new comments

• Reactivating Terminal

  #24699 commented on Jun 5, 2025 • 0 new comments

• Environment Activation Fails: Direct Path to conda.bat Used Instead of conda Command After 2/7 Extension Update

  #24801 commented on Jun 5, 2025 • 0 new comments

• selecting python interpreter has no effect, lsp server doesn't seem to be up

  #24839 commented on Jun 5, 2025 • 0 new comments

• Test discovery failure / regression for uniitest

  #24578 commented on Jun 9, 2025 • 0 new comments

• Run Selection/Line in already active python interpreter terminal rather than opening a new terminal

  #24960 commented on Jun 10, 2025 • 0 new comments

• "Run Python File" while python interpreter is in terminal will type the run command into the python interpreter

  #25159 commented on Jun 10, 2025 • 0 new comments

• New File hints

  #24994 commented on Jun 10, 2025 • 0 new comments

• 使用中文Command"Python.setinterpreter"not found

  #25040 commented on Jun 11, 2025 • 0 new comments

• [RFC] watch pyrefly settings

  #25041 commented on May 23, 2025 • 0 new comments

• Enable per test output correlation for pytest

  #22594 commented on May 14, 2025 • 0 new comments

• Problem executing multiple lines of code: ... versus >>>

  #25043 commented on May 14, 2025 • 0 new comments

• Smart send cell for VS Code Python Native REPL

  #24970 commented on May 18, 2025 • 0 new comments

• Remove Run Selection/Line in Terminal and Django from command palette

  #24139 commented on May 18, 2025 • 0 new comments

• [vscode ver. 1.100] Python environment incorrectly activated

  #25051 commented on May 22, 2025 • 0 new comments

• Create GitHub Action to check PyPI and open issue

  #22800 commented on May 23, 2025 • 0 new comments

• Django Testing Error

  #24657 commented on May 23, 2025 • 0 new comments

• Error while collecting test results (Socket communication)

  #24724 commented on May 23, 2025 • 0 new comments

• Unwanted debug output when running unittests.

  #24743 commented on May 23, 2025 • 0 new comments

• VSC will not recognize tests

  #24816 commented on May 23, 2025 • 0 new comments

• VSCode pytest data from WSL generate an error when processed

  #24811 commented on May 23, 2025 • 0 new comments

• Cannot run unittest in parallel anymore

  #24829 commented on May 23, 2025 • 0 new comments

• Pytest inline error reporting

  #24910 commented on May 23, 2025 • 0 new comments

• Pytest doesn't run in venv on Remote workstation and so fails

  #24841 commented on May 23, 2025 • 0 new comments

• function in parameter in parameterized test cause test to be skipped with 'ERROR: Not found' message.

  #24912 commented on May 23, 2025 • 0 new comments

• Tests are discovered but not ran

  #24913 commented on May 23, 2025 • 0 new comments

• Test Explorer is not reporting test status if a test is annotated with xdist_group

  #24935 commented on May 23, 2025 • 0 new comments

• Test discovery fails with pipe error on all repos

  #24966 commented on May 23, 2025 • 0 new comments

• unittest adapter: hang when tests are run in a separate process

  #25010 commented on May 23, 2025 • 0 new comments

• Tests starting with an Umlaut aren't registered by the testing environment

  #25015 commented on May 23, 2025 • 0 new comments

• Remove debugOptions when using python debug adapter

  #8104 commented on May 23, 2025 • 0 new comments

• Pytest.ini sudo option.

  #24411 commented on May 23, 2025 • 0 new comments

• Python test debugging falls back to default launch configuration after running custom `debug-test` configuration once

  #22530 commented on May 23, 2025 • 0 new comments

• Make it possible to add coverage to the existing state

  #24491 commented on May 23, 2025 • 0 new comments

• DocTest unittest discovery adapter

  #24601 commented on May 23, 2025 • 0 new comments

• More than a minute before first of 20k tests is shown as running

  #24514 commented on May 23, 2025 • 0 new comments

• Implement copying python import path from opened file

  #25027 commented on May 24, 2025 • 0 new comments

• Support profile-specific `terminal.activateEnvInCurrentTerminal` settings

  #20562 commented on May 25, 2025 • 0 new comments