October 2025 Python VS Code Update: Key Features and FAQs

<p>The October 2025 release of the Python extensions for Visual Studio Code brings several enhancements to improve your development workflow. Below are answers to common questions about the new features, including improvements to the Python Environments extension, a new <strong>Copy Test ID</strong> feature, and better shell startup reliability.</p> <h2 id="overview">1. What are the main highlights of the October 2025 Python extensions release?</h2> <p>This release focuses on three key areas: <a href="#environments">Python Environments extension improvements</a>, <a href="#copy-test-id">enhanced testing workflow with Copy Test ID</a>, and <a href="#shell-startup">shell startup improvements for Python environment activation</a>. The environments extension now handles conda environments more reliably by launching code directly without <em>conda run</em> and sorts Python versions in descending order for easier access to the latest releases. The testing workflow gains a convenient way to copy test identifiers from the gutter menu. Additionally, shell startup changes reduce issues where GitHub Copilot terminals weren't properly activating virtual environments, and virtual environment prompts now display correctly in PowerShell with shell integration.</p><figure style="margin:20px 0"><img src="https://uhf.microsoft.com/images/microsoft/RE1Mu3b.png" alt="October 2025 Python VS Code Update: Key Features and FAQs" style="width:100%;height:auto;border-radius:8px" loading="lazy"><figcaption style="font-size:12px;color:#666;margin-top:5px">Source: devblogs.microsoft.com</figcaption></figure> <h2 id="environments">2. What improvements were made to the Python Environments extension?</h2> <p>The Python Environments extension received several fixes and updates to enhance development experience. Key improvements include better performance and reliability when working with conda environments—now launching code directly without <em>conda run</em>. The environment flow is smoother with Python versions sorted in descending order for easier access to the latest releases. Crashes when running Python files that use <code>input()</code> have been fixed, and false-positive environment configuration warnings are reduced. The extension now <strong>automatically refreshes</strong> environment managers when expanding tree nodes, keeping your environment list up-to-date without extra steps. Community feedback helped identify and prioritize these improvements.</p> <h2 id="copy-test-id">3. How does the new "Copy Test ID" feature work?</h2> <p>The testing experience has been enhanced by adding a <strong>Copy Test ID</strong> option to the gutter icon context menu for test functions. When you right-click on a test icon in the editor gutter, you can now select "Copy Test ID" to quickly copy the test identifier in pytest format. This makes it easy to run specific tests from the command line or share test references with teammates. The feature streamlines the workflow, allowing you to bypass manual copying and reducing errors. For more details, refer to the <a href="https://code.visualstudio.com/docs/python/testing">VS Code testing documentation</a>.</p> <h2 id="shell-startup">4. What changes were made to shell startup for environment activation?</h2> <p>Shell startup has been improved to reduce issues where terminals created by <strong>GitHub Copilot</strong> weren’t properly activating Python virtual environments. The new approach provides more reliable environment activation across all terminal creation methods while reducing redundant permission prompts. Additionally, virtual environment prompts (e.g., <code>(.venv)</code>) now appear correctly when PowerShell is activated through shell integration. Issues with activation in WSL (Windows Subsystem for Linux) have also been resolved. These changes ensure a smoother experience when working with multiple Python environments and tools like Copilot.</p> <h2 id="config">5. What configuration is needed for the shell startup improvements?</h2> <p>To benefit from the shell startup improvements, you need to set the <code>python-envs.terminal.autoActivationType</code> setting to <strong>shellStartup</strong> in your VS Code settings. You can do this by opening the Command Palette (<code>Ctrl+Shift+P</code>), typing "Preferences: Open Settings (JSON)", and adding the line <code>"python-envs.terminal.autoActivationType": "shellStartup"</code>. Alternatively, you can search for the setting in the Settings UI. Once enabled, virtual environment activation will be more reliable across different terminal creation methods, including those spawned by GitHub Copilot.</p> <h2 id="other">6. What other minor changes and fixes are included in this release?</h2> <p>Several small enhancements and user-requested fixes have been added to improve your experience with Python and Jupyter Notebooks in VS Code. Notable changes include <strong>enhanced contributor experience</strong> with new Copilot Chat instruction files that provide guidance for testing features and understanding VS Code components when contributing to the Python extension. Additionally, various bug fixes and performance improvements have been made behind the scenes. For the complete list of changes, refer to the changelogs for the <a href="https://github.com/microsoft/vscode-python">Python extension</a> and <a href="https://github.com/microsoft/pylance-release">Pylance extension</a>.</p>