We are pleased to announce that the of the Extension for is now available. You can download the Python extension from the marketplace, or install it directly from the extension gallery in Visual Studio Code. You can learn more about Python support in Visual Studio Code in the VS Code documentation.

In this release we have closed a total of 38 issues including the stable release of our ptvsd 4 debugger, improvements to the language server preview, and other fixes.

In this release we are updating all users to the ptvsd 4.1.1 version of our Python debugger, providing a significant improvement to debugging performance and stability over the previous ptvsd 3.0 version. We originally announced an opt-in preview of ptvsd 4 in the February release of the Python extension, and have been continuing to improve on it based on user feedback. The new debug engine is built on top of the open source pydevd, which has allowed us to take advantage of its superior performance and support for third party libraries.

The new Python debugger supports the Logpoints feature added in the March iteration of VS Code. Logpoints allow you to essentially add print statements without having to stop execution. You can right-click on the margin and select “Add Logpoint…”, and then type in your message:

 

Remote debugging is easier to use and improved; previously you had to install the exact version of ptvsd used in VS Code on the remote server, and you needed to modify your code to enable the debugger to attach.

Now you can install any 4.x version of ptvsd and can enable attach from the command line. To install ptvsd and start remote debugging from the command line:

pip install --upgrade ptvsd
python3 -m ptvsd --host 1.2.3.4 --port 3000 -m myproject

Check out our updated remote debugging documentation for more information.

Once the server starts you can attach to it from VS Code. We are continuing to make improvements to the debugger, so stay tuned in our future releases.

In the July release of the Python extension we added a preview of the Microsoft Python Language Server, our Python analysis engine from Visual Studio hosted inside of VS Code. This allowed us to provide faster & richer completions including support for typeshed definitions. We have made the following improvements in this release:

  1. Language server now populates document outline with all symbols instead of just top-level ones. (#2050)
  2. Fixed issue in the language server when documentation for a function always produced “Documentation is still being calculated, please try again soon”. (#2179)
  3. Fix null reference exception in the language server causing server initialization to fail. The exception happened when search paths contained a folder that did not exist. (#2017)
  4. Fixed language server issue when it could enter infinite loop reloading modules. (#2207)
  5. Language server now correctly handles with statement when __enter__ is declared in a base class. (#2240)
  6. Fixed issue in the language server when typing dot under certain conditions produced null reference exception. (#2262)
  7. Language server now correctly merges data from typeshed and the Python library. (#2345)
  8. Code lenses now appear for unit tests when using the language server (#1948)

We have also added small enhancements and fixed issues requested by users that should improve your experience working with Python in Visual Studio Code. The full list of improvements is listed in our changelog, some notable improvements are:

  1. Ensure test count values in the status bar represent the correct number of tests that were discovered and run. (#2143)
  2. Ensure workspace pipenv environment is not labeled as a virtual env. (#2223)
  3. Fix visualstudio_py_testLauncher to stop breaking out of test discovery too soon. (#2241)
  4. Fix error when switching from new language server to the old Jedi language server. (#2281)
  5. Ensure stepping out of debugged code does not take user into PTVSD debugger code. (#767)

Be sure to download the Python extension for VS Code now to try out the above improvements. If you run into any issues be sure to file an issue on the Python VS Code GitHub page.



Source link

LEAVE A REPLY

Please enter your comment!
Please enter your name here