Overview

3 Pull requests merged by2 people

• Resolve REPL regression on indentation, disable PyREPL only when shell integration is enabled

  #25296 mergedJul 17, 2025

• fix: use latest pet

  #25287 mergedJul 14, 2025

• Return early in activate from env var collection

  #25286 mergedJul 14, 2025

1 Pull request opened by1 person

• Make PyREPL disabling conditional on shell integration setting for Python 3.13+

  #25281 openedJul 14, 2025

9 Issues closed by5 people

• Terminal python launch command not working ? or not stable ?

  #25293 closedJul 18, 2025

• Mention PyREPL is disabled when Python shell integration is enabled for Python3.13 and above

  #25240 closedJul 17, 2025

• Indentation regression with Python >= 3.13

  #25295 closedJul 17, 2025

• Terminal Environment Contributions: Path Modifications get Overwritten

  #25097 closedJul 17, 2025

• Terminal Venv auto activation not working

  #25288 closedJul 17, 2025

• Unable to activate conda python environment

  #25275 closedJul 14, 2025

• Automatic virtual environment activation under WSL in python doesn't work

  #25276 closedJul 14, 2025

• Shell won't start venv after update

  #25285 closedJul 14, 2025

• Pyenv virtualenvs not showing in `Python: Select Interpreter` command palette option

  #25239 closedJul 13, 2025

13 Issues opened by13 people

• After "Run Script", focus not move automatically

  #25302 openedJul 18, 2025

• Pytest isn't killed when stopping test sessions

  #25298 openedJul 18, 2025

• virtual environment is never activated by agent

  #25300 openedJul 17, 2025

• .env file no longer being applied

  #25294 openedJul 17, 2025

• Python extension not starting Pylance

  #25301 openedJul 17, 2025

• cant register env

  #25292 openedJul 16, 2025

• Terminal no longer auto-activating

  #25291 openedJul 16, 2025

• command prompt not have python PATH

  #25290 openedJul 16, 2025

• Inspect the contents of available environments

  #25289 openedJul 15, 2025

• VSCode does not activate my Python venv, despite displaying the correct interpreter

  #25284 openedJul 14, 2025

• Terminal prompt for uv venv was weird

  #25282 openedJul 14, 2025

• VS Code Python extension injects incorrect start up script oh-my-posh variables with shell integration

  #25280 openedJul 12, 2025

• auto complet

  #25279 openedJul 12, 2025

12 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.

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

  #25024 commented onJul 12, 2025 • 0 new comments

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

  #25067 commented onJul 12, 2025 • 0 new comments

• Django test discovering

  #24991 commented onJul 13, 2025 • 0 new comments

• Error when installing extension using VSIX file

  #25268 commented onJul 14, 2025 • 0 new comments

• 역슬러시와 따움표 생성 오류

  #25283 commented onJul 14, 2025 • 0 new comments

• ms-python uses a different Python version than selected

  #25267 commented onJul 14, 2025 • 0 new comments

• VS Code issues relating to new terminal activation feature

  #22879 commented onJul 15, 2025 • 0 new comments

• Virtual enviroment is not set correctly in Terminal

  #25185 commented onJul 15, 2025 • 0 new comments

• Python environment terminal activation breaks debugger launch

  #25192 commented onJul 16, 2025 • 0 new comments

• Coverage ignores report options

  #25086 commented onJul 17, 2025 • 0 new comments

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

  #25040 commented onJul 17, 2025 • 0 new comments

• Enable Python shell integration for 3.13 and above, when user opt-in

  #25242 commented onJul 17, 2025 • 0 new comments