Python v2021.3.0 Release Notes
Release Date: 2021-03-16 // about 3 years ago-
โจ Enhancements
- Activate the extension when the following files are found:
Pipfile
,setup.py
,requirements.txt
,manage.py
,app.py
(thanks Dhaval Soneji) (#4765) ๐ฒ 1. Add optional user-levelpython.tensorBoard.logDirectory
setting. When starting a TensorBoard session, use this setting if it is present instead of prompting the user to select a log directory. (#15476)
๐ Fixes
โ 1. Fix nosetests to run tests only once. (thanks djplt) (#6043)
- Make on-enter behaviour after
raise
much more like that ofreturn
, fixing handling in the case of pressing enter to wrap the parentheses of an exception call. (thanks PeterJCLaw) (#10583) ๐ง 1. Add configuration debugpyPath. (thanks djplt) (#14631) ๐ 1. Fix Mypy linter pointing to wrong column number (off by one). (thanks anttipessa, haalto, JeonCD and junskU) (#14978) - Show each python.org install only once on Mac when in discovery experiment. (#15302)
- All relative interpreter path reported start with
~
when in discovery experiment. (#15312) ๐ง 1. Remove FLASK_DEBUG from flask debug configuration to allow reload. (#15373) - Install using pipenv only if the selected environment is pipenv which is related to workspace folder, when in discovery experiment.
(#15489)
๐ 1. Fixes issue with detecting new installations of Windows Store python.
(#15541)
๐ฆ 1. Add
cached-property
package to bundled python packages. This is needed byjedi-language-server
running onpython 3.6
andpython 3.7
. (#15566) ๐ 1. Remove limit on workspace symbols when using Jedi language server. (#15576) - Use shorter paths for python interpreter when possible. (#15580)
- Ensure that jedi language server uses jedi shipped with the extension. (#15586) โก๏ธ 1. Updates to Proposed API, and fix the failure in VS Code Insider tests. (#15638)
Code Health
๐ 1. Add support for "Trusted Workspaces".
"Trusted Workspaces" is an upcoming feature in VS Code. (See: https://github.com/microsoft/vscode/issues/106488.) For now you need the following for the experience: - the latest VS Code Insiders - add `"workspace.trustEnabled": true` to your user settings.json At that point, when the Python extension would normally activate, VS Code will prompt you about whether or not the current workspace is trusted. If not then the extension will be disabled (but only for that workspace). As soon as the workspace is marked as trusted, the extension will activate. ([#15525](https://github.com/Microsoft/vscode-python/issues/15525))
โก๏ธ 1. Updates to the VSCode Notebook API. (#15567) โ 1. Fix failing smoke tests on CI. (#15573) โก๏ธ 1. Update VS Code engine to 1.54.0 (#15604)
- Use
onReady
method available on language client to ensure language server is ready. (#15612)
Thanks
Thanks to the following projects which we fully rely on to provide some of our features:
- debugpy
- isort
- jedi and parso
- jedi-language-server
- Microsoft Python Language Server
- ๐ Pylance
- exuberant ctags (user-installed)
- rope (user-installed)
Also thanks to the various projects we provide integrations with which help ๐ make this extension useful:
- ๐ Debugging support: Django, Flask, gevent, Jinja, Pyramid, PySpark, Scrapy, Watson
- Formatting: autopep8, black, yapf
- ๐ Interpreter support: conda, direnv, pipenv, pyenv, venv, virtualenv
- ๐ Linting: bandit, flake8, mypy, prospector, pylint, pydocstyle, pylama
- โ Testing: nose, pytest, unittest
And finally thanks to the Python development team and community for creating a fantastic programming language and community to be a part of!
- Activate the extension when the following files are found: