If you have any feedback or feature requests, you can file an issue on the Python environment manager’s GitHub repository. You can also create multiple terminals for different environments – once you click on the terminal icon next to an environment, it will automatically activate it.
You can then check which packages are installed in that environment as well as their versions. With the Python environment manager, you can open the manager view and see information on multiple Python environments located on your machine – even virtual environments not located in your workspace. While not an official Microsoft extension, we wanted to give it a shout-out to help spread the word about it! You can now inspect your Python environments and its packages with the Python Environment Manager extension! This extension is developed and maintained by Don Jayamanne, a member of our team and the creator of the Python extension. This change should impact only the local experience, and not remote debugging – attaching the debugger to remote processes running in Python 2.7 will still be supported. This is because our debugger, debugpy, will no longer Python 2.7 starting in January 2022.
An update on debugging with Python 2.7įollowing up last September’s announcement on limited IntelliSense support for Python 2.7, this is the last release with support for debugging locally with Python 2.7. We’re excited for you to give this new experience a try and welcome any feedback on the Pylance issue tracker.
Just like when using v or v, you can now take advantage of a series of editing features you might want when exploring a codebase virtually, or when inspecting the workspace locally to decide whether you’ll mark it as trusted. The Python extension now offers syntax error detection and limited IntelliSense support when using virtual or untrusted workspaces via Pylance. Rich Python editing experience when working with virtual or untrusted workspaces
With this preview, you can feel even more confident in the changes that are being made to your code and still save time when refactoring. You can also change your mind after seeing what would be changed at the preview stage and discard all changes. If you want to customize the references to be updated, you can toggle check boxes at the line or file level at the preview stage before accepting the changes. Previously, when you renamed a file/module, you would have searched for references to that module in your codebase and update each location manually.Īs of this release, after renaming a Python file/module, Pylance will find all the instances that need to be updated and provide you with a preview of all the changes to be made. One of our most heavily requested features is finally here! As of this release, you can now more easily refactor your code using a new rename refactoring experience, via Pylance.
If you’re interested, you can check the full list of improvements included in this release in our changelog.
You can download the Python extension from the Marketplace, or install it directly from the extension gallery in Visual Studio Code. We are pleased to announce that the December 2021 release of the Python Extension for Visual Studio Code is now available.