We're excited to announce that the November 2025 release of the Python extension for Visual Studio Code is now available!This release includes the following announcements: Add Copilot Hover Summaries as docstring Localized Copilot Hover Summaries Convert wildcard imports Code Action Debugger support for multiple interpreters via the Python Environments ExtensionIf you're interested, you can check the full list of improvements in our changelogs for the Python and Pylance extensions.Add Copilot Hover Summaries as docstringYou can now add your AI-generated documentation directly into your code as a docstring using the new Add as docstring command in Copilot Hover Summaries. When you generate a summary for a function or class, navigate to the symbol definition and hover over it to access the Add as docstring command, which inserts the summary below your cursor formatted as a proper docstring.This streamlines the process of documenting your code, allowing you to quickly enhance readability and maintainability without retyping.Localized Copilot Hover SummariesGitHub Copilot Hover Summaries inside Pylance now respect your display language within VS Code. When you invoke an AI-generated summary, you'll get strings in the language you've set for your editor, making it easier to understand the generated documentation.Convert wildcard imports into Code ActionWildcard imports (from module import *) are often discouraged in Python because they can clutter your namespace and make it unclear where names come from, reducing code clarity and maintainability.Pylance now helps you clean up modules that still rely on from module import * via a new Code Action. It replaces the wildcard with the explicit symbols, preserving aliases and keeping the import to a single statement. To try it out, you can click on the line with the wildcard import and press Ctrl + . (or Cmd + . on macOS) to select the Convert to explicit imports Code Action.Debugger support for multiple interpreters via the Python Environments ExtensionThe Python Debugger extension now leverages the APIs from the Python Environments Extension (vscode-python-debugger#849). When enabled, the debugger can recognize and use different interpreters for each project within a workspace. If you have multiple folders configured as projects—each with its own interpreter - the debugger will now respect these selections and use the interpreter shown in the status bar when debugging.To enable this functionality, set "python.useEnvironmentsExtension": true in your user settings. The new API integration is only active when this setting is turned on.Please report any issues you encounter to the Python Debugger repository.Other Changes and EnhancementsWe have also added small enhancements and fixed issues requested by users that should improve your experience working with Python in Visual Studio Code. Some notable changes include: Resolve unexpected blocking during PowerShell command activation (vscode-python-environments#952) The Python Environments Extension now respects the existing python.poetryPath user setting to specify which Poetry executable to use (vscode-python-environments#918) The Python Environments Extension now detects both requirements.txt and dev-requirements.txt files when creating a new virtual environment for automatic dependency installation (vscode-python-environments#506)We would also like to extend special thanks to this month's contributors: @iBug: Fixed Python REPL cursor drifting in vscode-python#25521Try out these new improvements by downloading the Python extension from the Marketplace, or install them directly from the extensions view in Visual Studio Code (Ctrl + Shift + X or ⌘ + ⇧ + X). You can learn more about Python support in Visual Studio Code in the documentation. If you run into any problems or have suggestions, please file an issue on the Python VS Code GitHub page.