LGTM!

command name LGTM

<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. --> It seems that VS Code now lets us customize the title of open dialogs: https://code.visualstudio.com/updates/v1_47#_open-and-save-dialog-title

If so, instead of "Open" we could say "Select Python interpreter"

<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Instead of having multiple settings for each linter, we can now redesign the settings to use the new VS Code object editor: https://code.visualstudio.com/updates/v1_47#_edit-object-settings-from-the-settings-editor

<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. --> https://code.visualstudio.com/updates/v1_47#_single-file-debugging

@zhangxiang1209 this seems to be a Python extension issue. Would you mind trying out our new language server to see if it solves your issue? Otherwise we'd be happy to assist you in our GitHub repo.

import cube
# Error: RuntimeError: file C:\Program Files\Autodesk\Maya2020\Python\lib\site-packages\debugpy\server\api.py line 224: timed out waiting for adapter to connect # 

cube.py:

import maya.cmds as mc
import debugpy 
import time

#while debugpy.is_client_connected():
#    time.sleep(0.5)

debugpy.listen(("localhost",5678))
debugpy.wait_for_client()

debugpy.breakpoint()
r = mc.polyCube(w=2,h=9,d=2)

debugpy.breakpoint()
print("hey!")

Run selection for "import cube"

When not calling listen

<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. --> If you copy the path to the interpreter from somewhere and accidentally leave a space in it, interpreter selection fails. It'd be nice if we could remove whitespaces from the beginning of paths that are entered

I was trying to learn more about how component governance works on AzDo but the links in the documentation doesn't seem to work

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 1e1faa66-8ae6-572c-233d-01fdbca29caf
• Version Independent ID: ee5297ca-c3e8-5c33-24dc-e4bd2c72fcea
• Content: Overview - Azure DevOps Services REST API
• Content Source: docs-ref-conceptual/5.1/componentGovernance/index.md
• Product: vs-devops-alm
• Technology: vs-devops-integrate
• GitHub Login: @wnjenkin
• Microsoft Alias: whjenkin

(not actually a duplicate but we'll include this into the spec for #6544)

Environment data

• VS Code version: 1.45.1
• Extension version: 2020.5.80290
• OS and version: macOS 10.15.4
• Python version: 3.8
• Type of virtual environment used: conda
• Jedi or Language Server? Language
• Value of the python.languageServer setting: Microsoft

Expected behaviour

That setting PYTHONPATH to include a src directory with terminal.integrated.env.* (see below) also affects (a) test discovery, and (b) interactive debugging in VS Code.

  "terminal.integrated.env.linux": {
    "PYTHONPATH": "${workspaceFolder}/src:${env:PYTHONPATH}"
  },
  "terminal.integrated.env.osx": {
    "PYTHONPATH": "${workspaceFolder}/src:${env:PYTHONPATH}"
  },
  "terminal.integrated.env.windows": {
    "PYTHONPATH": "${workspaceFolder}/src;${env:PYTHONPATH}"
  },

Actual behaviour

• For test discovery: test discovery fails because packages in src cannot be imported.
• For debugging: debugging also fails because packages in src cannot be imported.

Workarounds

• Current workaround for test discovery: additionally set PYTHONPATH=src in a .env file.
• Current workaround for debugging: see https://github.com/microsoft/vscode-python/issues/11875.

Steps to reproduce:

Same steps to reproduce as in https://github.com/microsoft/vscode-python/issues/11875, which is a related issue.

Duplicate of https://github.com/microsoft/vscode-python/issues/6544

I opened https://github.com/microsoft/vscode-docs/issues/3856 to track the documentation update that is required.

Related: #11812

Reported in https://github.com/microsoft/vscode-python/issues/5705

In this section: https://github.com/microsoft/vscode-docs/blob/master/docs/python/environments.md#variable-substitution we mention that any existing environment variable could be used when defining an environment variable. But to make it work we need to add {env:VARIABLE_NAME} instead of {VARIABLE_NAME} for it to work when running Python files in the extension.

For example:

1. Create .env file with a single line PATH="${PATH};Blah-blah-blah".
2. Create a Python file with print(os.environ.get('PATH'))
3. Run Python file with the play button

In this case, ;Blah-blah-blah gets printed. If we change the .env file to get $(env:PATH), then it works. So we should update our docs accordingly

<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

I ran my tests and had them passing. Then I moved all of my logic code and broke my imports, but the Test Explorer continued to say my tests were passing. The following is an example of the failures pytest is reporting which are not being reflected in the Test Explorer (the status bar shows the right result):

=================================== ERRORS ====================================
______________ ERROR collecting tests/test_ghutils/test_ping.py _______________
ImportError while importing test module 'c:\Users\brcan\Repositories\pvscbot\tests\test_ghutils\test_ping.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests\test_ghutils\test_ping.py:7: in <module>
    from pvscbot.ghutils import ping
E   ModuleNotFoundError: No module named 'pvscbot.ghutils'

Closing in favour of #4586.

Treat the extension as 3 separate projects:

• UI Extension code
  • This excludes debugger code (that runs in a separate process)
  • This excludes our tests
• Extension Debugger Code
  • This excludes debugger code (that runs in a separate process)
  • This excludes our tests
• Tests
  • Just compile everything, for tests

Why the separation

• We can let the compiler pick up bugs in our code
• I.e. compiler can ensure extension does NOT use code from the debugger
  • I.e. fixes https://github.com/Microsoft/vscode-python/issues/3939
• I.e. compiler can ensure extension does NOT use code from our tests
  • I.e. fixes https://github.com/Microsoft/vscode-python/issues/1758
  • We still have this happening today, now its leaking in because WebPack pulls stuff in silently..
• setTimeout issues in node.js and browser world.
  • Compiler can get confused with what setTimeout returns. A number of Nodejs.timer! This is because the extension uses both types, to compile DS code and extension code.

Summary

• Two issues can be traditionally solved in a complicated way using linters, refactoring, etc, when it can easily be solved via a compilation step.
• Cheaper option.

Closing as stale

<!-- Do you have a question instead of a bug report or enhancement request? Please ask it on https://stackoverflow.com/questions/tagged/visual-studio-code+python.

Unable to install a linter or formatter? 'No installers available'? Windows - https://stackoverflow.com/questions/4750806/how-do-i-install-pip-on-windows Linux - https://www.cyberciti.biz/faq/debian-ubuntu-centos-rhel-linux-install-pipclient/ , https://www.tecmint.com/install-pip-in-linux/

Python configuration issues? Please check https://code.visualstudio.com/docs/python/python-tutorial#_prerequisites

Otherwise please fill in the requested details below. "XXX" markers should not be present in the final bug report.

If you think a GIF of what is happening would be helpful, consider tools like https://www.cockos.com/licecap/, https://github.com/phw/peek or https://www.screentogif.com/ . -->

Environment data

• VS Code version: 1.33.1
• Extension version (available under the Extensions sidebar): 2019.3.6558
• OS and version: Ubuntu 18.04
• Python version (& distribution if applicable, e.g. Anaconda): 3.6.1 (Docker)
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv

Expected behaviour

Is there / would there be a way to set default host for the debug server? Currently it can be set per launch configuration, but test launcher doesn't use launch configuration yet. I'm looking at https://github.com/Microsoft/vscode-python/pull/4372 but ITestDebugConfig doesn't seem to have host config.

My use case: I would like to configure it to 0.0.0.0 instead of 127.0.0.1. Because VS Code doesn't support remote interpreter for Docker yet, I'm using a bridge script to make it look like a local python interpreter. The only problem left is that I need the Docker python to be able to connect to the debug server at 172.17.0.1 (the default Docker host IP in Linux).

I prefer to use "launch" request instead of "attach" to not have to add ptvsd inside my code every time I need to debug something.

My workaround is to edit out/client/debugger/debugAdapter/main.js and set the default there. But hopefully it can be configured soon.

Closing as this should be addressed with the Docker extension.

Closing as stale.

Currently the tests are just not manageable, nor readable. src/test/unittests/pytest/pytest.run.test.ts

related to #8196

Currently when the test explorer displays '.' as items. As a user this is confusing and pointless.

Closing as we can't repro this anymore.

@DonJayamanne do you mean that it should open the file with the test once we double click on it in the file explorer?

• Ensure linter output is mocked to test linters
• Ensure linter is invoked to confirm messages are returned

Now that we're bundling the source and dependencies using webpack, stack traces are useless when users come across errors. Source maps needs to be explicitly enabled. As the debug adapter runs in a different process, the process used to enable source map support is not as straightforward as implementing in in the extension process.

Solution: We need to wait for the next release of VSC for new API

update the docs: https://code.visualstudio.com/docs/python/debugging#_debugging-specific-app-types

Related: https://github.com/microsoft/vscode-python/issues/11864

We can add a shortcut to execute the "Run test" code lens containing block.

When I click the "Run Python File in Terminal" button, if a program is already running, it will not be interrupted; instead it will just try to paste the python command into the terminal. This also may be interpreted as input to the already running command.

Environment data

• VS Code version: 1.45.1
• Extension version (available under the Extensions sidebar): 2020.5.80290
• OS and version: Windows 10.0.18363 Build 18363
• Python version (& distribution if applicable, e.g. Anaconda): Python 3.8.1
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
• Relevant/affected Python packages and their versions: N/A
• Relevant/affected Python-related VS Code extensions and their versions: N/A
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): Jedi
• Value of the python.languageServer setting: Microsoft

Expected behaviour

An existing script run will be killed and the new script run will execute in the terminal

Actual behaviour

The script will continue running and the new run command is pasted as keyboard input

Steps to reproduce:

1. Open python script which doesn't terminate immediately
2. Click "Run Python File in Terminal"
3. Modify script
4. Click "Run Python File in Terminal" again
5. The original version keeps running

Duplicate of https://github.com/microsoft/vscode-python/issues/11812.

<!-- Please search existing issues to avoid creating duplicates. --> This issue is similar to #2470 but the solution doesn't apply to me. I tried changing the "python.venvPath": "${workspaceFolder}/venv" in setting.json but it didn't help. As it can be seen in the screenshot, I can use the virtual environment using terminal.

Environment data

• VS Code version: 1.45.1
• Extension version (available under the Extensions sidebar): 2020.5.80290
• OS and version: ubuntu 18.04 (Linux x64 4.15.0-101-generic)
• Python version (& distribution if applicable, e.g. Anaconda): python 3.6.9
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
• Relevant/affected Python packages and their versions: XXX
• Relevant/affected Python-related VS Code extensions and their versions: XXX
• Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): true
• Value of the python.languageServer setting: "Microsoft"

Expected behaviour

Clicking on the interpretor on the left bottom should show all available interpretors including virtual environments.

Actual behaviour

virtual environment are not detected.

Steps to reproduce:

1. click on the interpretor selection on the left bottom

Logs

We decided we won't look for environments in sub-directories for performance reasons. The problem that was mentioned in this comment will be addressed once we ship our python.pythonPath changes to all users (#11015).

VS Code will create directories when creating files that include a /. When that file is a .py, it would be nice to create the necessary __init__.py as well.

For bonus points, it would be nice to create __init__.pyi when creating a filename ending in .pyi.

Thanks for the suggestion! We talked about it with the team and we have unfortunately decided we will not be moving forward with this idea. We think there isn't an enough widespread need for this to warrant the maintenance cost for the feature.

I'm also reproducing it 100% of the time and I'm on Windows

<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. --> It's likely the cause of the performance issues with activation since the May release. We can just look for this file in the root of the workspace instead

@jahan01 it's actually used by Pyright. We just added a rule to auto activate the Python extension for pyright users.

yes agreed. related: https://github.com/microsoft/vscode-python/issues/9543, https://github.com/microsoft/vscode-python/issues/9622, https://github.com/microsoft/vscode-python/issues/9609

great point, thanks for bringing this up, @cncolder!

I can also repro it:

• VS Code version: 1.47.0-insider
• Extension version: 2020.6.91350
• Environment: Python 3.8.3 (64 bit) -- a venv is selected in the workspace but the kernel started from the global environment
• Jupyter version:

jupyter core     : 4.6.3
jupyter-notebook : 6.0.3
qtconsole        : 4.7.4
ipython          : 7.15.0
ipykernel        : 5.3.0
jupyter client   : 6.1.3
jupyter lab      : not installed
nbconvert        : 5.6.1
ipywidgets       : 7.5.1
nbformat         : 5.0.7
traitlets        : 4.3.3

Developer tools: logjuly2020.txt

Output channel:

User belongs to experiment group 'RunByLine - experiment'
User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
User belongs to experiment group 'UseTerminalToGetActivatedEnvVars - control'
User belongs to experiment group 'LocalZMQKernel - experiment'
User belongs to experiment group 'CollectLSRequestTiming - control'
User belongs to experiment group 'CollectNodeLSRequestTiming - experiment'
User belongs to experiment group 'EnableIPyWidgets - experiment'
User belongs to experiment group 'CustomEditorSupport - control'
> conda --version
> pyenv root
> python3.7 c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3.6 c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python3 c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python2 c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> python c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> py -3.7 c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> py -3.6 c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> py -3 c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> py -2 c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> ~\OneDrive - Microsoft\feedback\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import sys;print(sys.executable)"
> conda info --json
Python interpreter path: ~\OneDrive - Microsoft\feedback\venv38\Scripts\python.exe
Starting Pylance language server.
> ~\OneDrive - Microsoft\feedback\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import ipykernel"
> conda --version
> ~\OneDrive - Microsoft\feedback\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import ipykernel"
> ~\OneDrive - Microsoft\feedback\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import ipykernel"
> c:\Users\luabud\Apps\hello\env38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import jupyter"
> c:\Users\luabud\Apps\hello\env38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import notebook"
> c:\Users\luabud\Apps\hello\env38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py jupyter kernelspec --version
> ~\OneDrive - Microsoft\feedback\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import ipykernel"
> ~\OneDrive - Microsoft\feedback\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_launcher_daemon -v
> c:\Users\luabud\Apps\feedback - Copy\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_launcher_daemon -v
> ~\OneDrive - Microsoft\feedback\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_launcher_daemon -v
> c:\Users\luabud\Apps\hello\env38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v
> c:\Users\luabud\Apps\hello\env38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v
> c:\Users\luabud\Apps\hello\env38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.jupyter_daemon -v
> ~\OneDrive - Microsoft\feedback\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py -c "import ipykernel"
> c:\Users\luabud\Apps\feedback - Copy\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_launcher_daemon -v
> ~\OneDrive - Microsoft\feedback\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_launcher_daemon -v
> c:\Users\luabud\Apps\feedback - Copy\venv38\Scripts\python.exe c:\Users\luabud\.vscode-insiders\extensions\ms-python.python-2020.6.91350\pythonFiles\pyvsc-run-isolated.py pip --version
Python interpreter path: .\venv38\Scripts\python.exe

FWIW Pyright is included in Pylance, that was just released: https://devblogs.microsoft.com/python/announcing-pylance-fast-feature-rich-language-support-for-python-in-visual-studio-code/

@kynan we already have an API that allows for extensions to retrieve the value of the selected environment, but we're making some final updates on it: https://github.com/microsoft/vscode-python/issues/12596

• Fixes "no module read_dotenv" error (requirements.txt contains python-dotenv but read_dotenv comes from django-dotenv)
• Adds psycopg2-binary v2.7.5 by default, comments out line for installing v2.7.4
• Hides line for disabling whitenoise (that for some reason started causing errors for me)
• Updates several packages for fixing vulnerabilities (through npm audit fix and by updating serialize-javascript to 2.1.1 - to stop warning from GH)

Closing this PR since I fixed this issue and others here: https://github.com/microsoft/python-sample-tweeterapp/pull/13

Sorry that it took me forever to reply to this!

You're right Ian, I could not start a Jupyter server from that environment. FWIW the path that was set into the HOME key on the pyvenv.cfg was this one: C:\Users\luabud\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\python.exe And it seems that pip isn't available in this environment, so I guess something funky happened when I created it.

I'm using a new virtual environment so things are working well now 😊

For https://github.com/microsoft/vscode-python/issues/12614

<!-- If an item below does not apply to you, then go ahead and check it off as "done" and strikethrough the text, e.g.: - [x] ~Has unit tests & system/integration tests~ -->

• [x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
• [x] Title summarizes what is changing.
• [x] Has a news entry file (remember to thank yourself!).

For https://github.com/microsoft/vscode-python/issues/12614

<!-- If an item below does not apply to you, then go ahead and check it off as "done" and strikethrough the text, e.g.: - [x] ~Has unit tests & system/integration tests~ -->

• [x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
• [x] Title summarizes what is changing.
• [x] Has a news entry file (remember to thank yourself!).

<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. --> It's likely the cause of the performance issues with activation since the May release. We can just look for this file in the root of the workspace instead

Purpose

<!-- Describe the intention of the changes being proposed. What problem does it solve or functionality does it add? --> Since there's a bug in codespaces that makes the play button not appear sometimes (https://github.com/MicrosoftDocs/vsonline/issues/505), I'm replacing the step to run the file in the terminal.

Does this introduce a breaking change?

<!-- Mark one with an "x". -->

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

<!-- Please check the one that applies to this PR using "x". -->

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code

hey folks! any updates on this by any chance? 😊

<!-- If an item below does not apply to you, then go ahead and check it off as "done" and strikethrough the text, e.g.: - [x] ~Has unit tests & system/integration tests~ -->

• [x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
• [x] Title summarizes what is changing.

<!-- If an item below does not apply to you, then go ahead and check it off as "done" and strikethrough the text, e.g.: - [x] ~Has unit tests & system/integration tests~ -->

• [x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
• [x] Title summarizes what is changing.

It'd be nice to add a "Run last executed test" command that would allow for that. If no tests have run, then it'd do nothing.

There should be no spaces by default inside the """.
Example: """Comments on a single line."""

If there's a text selection on multiple lines, the """ should be placed on separated lines above and below the selected lines.
Example:

"""
Comments on
multiple lines.
"""

I think that should be the default but it would be even better if you provide a setting to choose whether the starting quotes must be on a line by itself or not.
Example:

"""Comments on
multiple lines.
"""

And the "toggle block comment" should be improved to uncomment the whole block when we executed the command with the cursor anywhere inside the comment or having a selection inside the comment.

See PEP-257.
Practical examples (Django): single line and multiline.

Thanks for the suggestion! We talked about it with the team and we have unfortunately decided we will not be moving forward with this idea. We think there isn't an enough widespread need for this to warrant the maintenance cost for the feature.

@bersbersbers did you add this to your User settings (View > Command Palete... and run "Preferences: Open Settings (JSON))?

If so, please do open a separate issue.

Thanks for the suggestion! We talked about it with the team and we have unfortunately decided we will not be moving forward with this idea. We think there isn't an enough widespread need for this to warrant the maintenance cost for the feature.

Hi! VS Code offers package info hover tooltips out of the box for npm's package.json, but even with this extension there's no similar feature for pip's requirements.txt. I've made an extension which patches that and adds such tooltips, but could we get that into ms-python.python? I could implement that and make a pull request if that'd sit right with you.

Here's my execution of the idea:

I don't see deprecated as wrong, but I like the wording for "no longer used by the Python extension" 😊

Lots of great discussions here! One thing to notice is that for Python our green play button calls our "Run Python in Terminal" command, which calls the path to the selected Python interpreter and appends the file path to it:

That means that we have a different concept for "Run", "Run without debugging" and "Debug".

The feedback we hear from our users is that they'd love to customize the play button (https://github.com/microsoft/vscode-python/issues/10130, https://github.com/microsoft/vscode-python/issues/11036, https://github.com/microsoft/vscode-python/issues/11473, https://github.com/microsoft/vscode-python/issues/12509). So we thought of binding the icon to "Run without debugging" with the default configuration for Python files (bonus points if we could follow what is done for NodeJS has auto configure it - for Django and Flask apps for example 😁).

I like the idea of having different icons and being able to toggle between them. Another thing I thought of would be if VS Code provided just one icon ($(play)) and made it configurable so that users (and maybe extensions) could change what behaviour it's bind to.

@ericsnowcurrently Let's start with pyproject.toml first to be conservative, then we can add setup.py as if we don't receive complaints.

@int19h I like it! An alternative would be to have python.debuggerVariablePresentation, but I prefer your suggestion because it goes with our other settings (python.testing, python.linting, etc.). I don't foresee us having many settings for debugging in the settings.json file, but I think it's good to follow our standard format.

Thanks for reporting this! The requirements.txt file was updated in https://github.com/microsoft/python-sample-tweeterapp/pull/13, so that should fix it 😊 let me know if it didn't though!

Thanks @mishagin-tim for bringing it up! I updated the packages, it's working for me but it'd be great if others could confirm 😊

For https://github.com/microsoft/python-sample-tweeterapp/issues/12

For https://github.com/microsoft/python-sample-tweeterapp/issues/12

The description seemed like a "true"/"false" value to me, but hopefully having "shell" as an option clarifies that the 'pass all values as is' refers to "none". In short, LGTM 😁.

The issue is in the Python extension, it's the same root cause of https://github.com/microsoft/vscode-python/issues/12481. It's fixed in our Insiders build, and we'll release the fix as soon as we can.
The workaround out of the Insiders build is here.

@int19h I think we will want to change our default Remote attach configuration to use it (and perhaps create an issue to remove "host" and "port" from the top-level in the launch.json schema if that wasn't part of the updates?). But I believe these can be tracked as separate items if you think that would make sense 😊

I agree with you @int19h, it makes sense to have it as a User setting (I don't see how someone would like to disable this per project?).

@DonJayamanne about this:

else we end up with more settings in settings.json that are probably not going to be used by a majority of the users.

I feel that this is already the case for VS Code all up, isn't it? Perhaps I'm biased because I love the power of customization in VS Code, so I'd love to have this in the extension too.

Thanks for bringing this up, folks! I opened https://github.com/microsoft/vscode-docs/issues/3789 so we can update our docs to reflect that 😊

@yuvadm our plan is to deprecate the pythonPath setting, so you'll still be able to select interpreters per workspace but that info won't be stored in the settings.json file. We have this change on as an experiment, you can learn more about it here: https://github.com/microsoft/vscode-python/wiki/AB-Experiments#experiment---deprecatepythonpath

This was raised here: https://github.com/microsoft/vscode-python/issues/12164#issuecomment-642975508.

We just need to update this section: https://code.visualstudio.com/docs/python/environments#_where-the-extension-looks-for-environments

😊

Hi @Blotuxs, this seems to be an issue in the Python extension so I opened an issue on the other repo 😊.

From https://github.com/MicrosoftDocs/intellicode/issues/199

Hi

About a month ago Intellicode showed me recommendations for the Openpyxl library in Python. And since a few days ago it does not show all the recommendations (As seen in the image it does not show the Cell recommendation or others).

Try reinstalling Visual Studio Code, Openpyxl, Python and Intellicode but it doesn't work.

Try to delete the Extensions folder and download it again.

Settings: "python.jediEnabled": false "python.languageServer": "Microsoft"

I would appreciate any recommendation. Thank, in advance.