We have announced that the February 2020 release of the Python extension for Visual Studio Code is available. Everybody can download the Python extension from the marketplace, or install it directly from the extensions in Visual Studio Code.Subscribe to Latest Articles
Enter your email address Useful Links For Authors
Article Writing Tips
Why Submit Articles
HomeInternetVideo MarketingLearn About February 2020 Release – Python in Visual Studio CodeLearn About February 2020 Release – Python in Visual Studio Code
Learn About February 2020 Release – Python in Visual Studio Code
Harsh Kumar Sharma PhotoBy Harsh Kumar Sharma on March 03, 2020 0
Powered by Google TranslateTranslate
We have announced that the February 2020 release of the Python extension for Visual Studio Code is available. Everybody can download the Python extension from the marketplace, or install it directly from the extensions in Visual Studio Code.
If you have already installed the Python extension, you will also get the latest updates by restarting the Visual Studio code or updating directly to the extensions view. Learn more about Python for GIS support in the Visual Studio Code in the documentation and for more help python development
In this release we made improvements to be listed in our changelog, closing a total of 66 issues, including a fast startup of the Jupiter notebook editor and scaling of configuration information. Keep reading to find out more!
Jupiter notebook editor starts fast.
In the January release of Python Expansion, we made a tremendous improvement in the performance of the notebook editor. In this release, we kept trying to take it further. In our test benchmark, we see an additional 2-3X improvement in speed when starting the Jupiter server and opening the notebook editor. The first cell execution is also faster because now the Jupiter server automatically begins in the background when the notebook opens.
Scaling Back of Configuration Notification
The response often got visitors and open a workspace for Studio Code without selecting interspace. The Python extension tool requires a lot of installation was throwing away all the information. Previously, the installation failed because no interpreter was selected in the workspace.
In this release, we scaled back notifications for tool installations. They are only displayed if an interpreter is selected.
Although it is not part of the new improvements included in this release, the Python debugger supports a feature that is not known: Jump to Cursor.
Whenever you start a debug session, and the debugger hits the breakpoint, you can right-click at any part of your code – before and after the point where the breakpoint hits, and “jump to” Cursor “. This will allow the debugger to continue. Its execution from that selected line:
If you want to execute code that debugger has already run, you don’t have to restart the debug session and wait for execution to reach that point again. You can go to the line you want to execute.
Call for action!
Do you know about this feature before this blog post? Do you think its name could be improved to indicate its behavior better?
Enhancements and Changes
In this release, small enhancements are also added and fixed issues requested by users that should improve your experience of working with Python in the Visual Studio Code. Some notable changes include:
Start Jupiter Server automatically when you open a notebook or interactive window. (# 7232) The output panels are not displayed when creating a workspace symbol. (# 9603)
Fix an accident when using priestess to search with unknown line numbers. (Thanks to Olivier Grisel) (# 7487)
Update Chinese (traditional) translation. (Thanks Pan 93412) (# 9548)
We are testing new features. If you see something different, which is not announced by the team, and you can be a part of the experiment! To see an experiment, and check the first lines in the Python extension output channel. If you want to exit the A / B exam, you can open User Settings. Open the JSON file (see> Command Palette … and Preferences: Open Settings (JSON)) and set it to “python.experiments.opt-out” [“all”], or for specific experiments you opt-out Want to do