You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create an environment with a space in their path somewhere as well as upper and lowercase characters
Make sure that you do not have python.pythonPath specified in your settings.json when testing automatic detection
Do note that the Select Interpreter drop-down window scrolls
Detected a single virtual environment at the top-level of the workspace folder on Mac when when python command points to default Mac Python installation or python command fails in the terminal.
Appropriate suffix label specified in status bar (e.g. (venv))
Detected a single virtual environment at the top-level of the workspace folder on Windows when python fails in the terminal.
Appropriate suffix label specified in status bar (e.g. (venv))
Detected a single virtual environment at the top-level of the workspace folder
Appropriate suffix label specified in status bar (e.g. (venv))
"python.terminal.activateEnvironment": false deactivates automatically running the activation script in the terminal
After the language server downloads it is able to complete its analysis of the environment w/o requiring a restart
(Linux/macOS) Virtual environments created under {workspaceFolder}/.direnv/python-{python_version} are detected (for direnv and its layout python3 support)
Appropriate suffix label specified in status bar (e.g. (venv))
Uh oh!
There was an error while loading. Please reload this page.
Test plan
Environment
Tests
ALWAYS:
Output
window underPython
for logged errorsDeveloper Tools
open to detect any errorsEnvironment
Interpreters
Select Interpreter
command"python.pythonPath"
triggers an update in the status barRun Python File in Terminal
Run Selection/Line in Python Terminal
Shift+Enter
Virtual environments
ALWAYS:
Use the latest version of Anaconda
Realize that
conda
is slowCreate an environment with a space in their path somewhere as well as upper and lowercase characters
Make sure that you do not have
python.pythonPath
specified in yoursettings.json
when testing automatic detectionDo note that the
Select Interpreter
drop-down window scrollsDetected a single virtual environment at the top-level of the workspace folder on Mac when when
python
command points to default Mac Python installation orpython
command fails in the terminal.(venv)
)Detected a single virtual environment at the top-level of the workspace folder on Windows when
python
fails in the terminal.(venv)
)Detected a single virtual environment at the top-level of the workspace folder
(venv)
)Create Terminal
works"python.terminal.activateEnvironment": false
deactivates automatically running the activation script in the terminalDetect multiple virtual environments contained in the directory specified in
"python.venvPath"
Detected all conda environments created with an interpreter
(condaenv)
)Create Terminal
works"python.terminal.activateEnvironment": false
deactivates automatically running the activation script in the terminal(Linux/macOS until
-m
is supported) Detected the virtual environment created by pipenv(pipenv)
)pipenv install --dev
Create Terminal
works"python.terminal.activateEnvironment": false
deactivates automatically running the activation script in the terminal(Linux/macOS) Virtual environments created under
{workspaceFolder}/.direnv/python-{python_version}
are detected (for direnv and itslayout python3
support)(venv)
)Environment files
Sample files:
ALWAYS:
Make sure to use
Reload Window
between tests to reset your environmentNote that environment files only apply under the debugger and Jedi
Environment variables in a
.env
file are exposed when running under the debugger"python.envFile"
allows for specifying an environment file manually (e.g. Jedi picks upPYTHONPATH
changes)envFile
in alaunch.json
configuration worksDebugging
pythonPath
setting in yourlaunch.json
overrides yourpython.pythonPath
default settingLinting
ALWAYS:
Problems
tab to see e.g. if a linter is raising errorsPylint/default linting
[Prompting to install Pylint is covered under
Environments
above]For testing the disablement of the default linting rules for Pylint:
--user
for system-install of Python"python.linting.pylintUseMinimalCheckers": false
turns off the default rules w/ nopylintrc
file presentpylintrc
file turns off the default rulesOther linters
Note:
You can use the
Run Linting
command to run a newly installed linterWhen the extension installs a new linter, it turns off all other linters
flake8 works
Select linter
lists the linter and installs it if necessarymypy works
Select linter
lists the linter and installs it if necessarypep8 works
Select linter
lists the linter and installs it if necessaryprospector works
Select linter
lists the linter and installs it if necessarypydocstyle works
Select linter
lists the linter and installs it if necessarypylama works
Select linter
lists the linter and installs it if necessary3 or more linters work simultaneously (make sure you have turned on the linters in your
settings.json
)Run Linting
runs all activated linters"python.linting.enabled": false
disables all lintersEnable Linting
command changes"python.linting.enabled"
"python.linting.lintOnSave
worksEditing
IntelliSense
Please also test for general accuracy on the most "interesting" code you can find.
"python.autoComplete.extraPaths"
works"python.autocomplete.addBrackets": true
causes auto-completion of functions to append()
Formatting
Sample file:
Format Document
is runautopep8
worksblack
worksyapf
works"python.formatting.provider"
is specified but not matching*Path
or*Args
settings)*Path
and*Args
settings are specified (use absolute paths; use~
if possible)"editor.formatOnType": true
works and has expected resultsRefactoring
Extract Variable
worksrope
if it is not already availableExtract method
worksrope
if it is not already availableSort Imports
worksDebugging
ALWAYS:
Test the current debugger
Test the experimental debugger (and note whether it is at least as fast as the old debugger)
Configurations work (see
package.json
and the"configurationSnippets"
section for all of the possible configurations)Running code from start to finish w/ no special debugging options (e.g. no breakpoints)
Breakpoint-like things
Stepping
Can inspect variables
Variables
section of debugger sidebarRemote debugging works
App Engine
Unit testing
unittest
Run All Unit Tests
triggers the prompt to configure the test runnerRun Test
worksDebug Test
workstest_setup
method to verify)pytest
Run All Unit Tests
triggers the prompt to configure the test runnerpytest
gets installedRun Test
worksDebug Test
worksDiagnostic
is shown in the problems pane for each failed/skipped testDiagnostic
s are organized according to the file the test was executed from (not neccesarily the file it was defined in)DiagnosticRelatedInformation
is shown for eachDiagnostic
DiagnosticRelatedInformation
reflects the traceback for the testnose
Run All Unit Tests
triggers the prompt to configure the test runnerRun Test
worksDebug Test
worksGeneral
Run Test
lens works (and status bar updates as appropriate)Debug Test
lens worksRun All Unit Tests
worksDiscover Unit Tests
works (resets tests result display in status bar)Run Unit Test Method ...
worksView Unit Test Output
worksRun Failed Tests
worksThe text was updated successfully, but these errors were encountered: