Repository navigation
Closed as not planned
Labels
experimentingFeature is part of an experimentFeature is part of an experimenttriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team
Description
Type: Bug
Behaviour
Expected vs. Actual
Expected
When opening the terminal only one bash prompt should appear.
Example:
Actual
Only when .venv is defined in the extension as the interpreter path, opening the terminal results in a double prompt.
Example:
This behavior does not reproduce in regular bash:
Only in VSCode terminal, and only when the extension has the .venv defined as the interpreter.
Steps to reproduce:
- Open a workspace with a venv
- Set the venv as the python interpreter
- Open the terminal
Diagnostic data
- Python version (& distribution if applicable, e.g. Anaconda): 3.10.12
- Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
- Value of the
python.languageServersetting: Default
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
(No output)
User Settings
languageServer: "Pylance"
testing
• pytestArgs: "<placeholder>"
• pytestEnabled: true
Extension version: 2023.16.0
VS Code version: Code 1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d, 2023-09-14T05:55:25.390Z)
OS version: Windows_NT x64 10.0.25951
Modes:
Remote OS version: Linux x64 5.15.90.1-microsoft-standard-WSL2
System Info
| Item | Value |
|---|---|
| CPUs | 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 1805) |
| GPU Status | 2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled |
| Load (avg) | undefined |
| Memory (System) | 15.73GB (2.34GB free) |
| Process Argv | --folder-uri vscode-remote://wsl%2Bubuntu/home/eavron/repos/wifi_drv-potato_farm --crash-reporter-id c7e1b94c-8c18-46fa-a223-594c5a29f1cb |
| Screen Reader | no |
| VM | 0% |
| Item | Value |
|---|---|
| Remote | WSL: Ubuntu |
| OS | Linux x64 5.15.90.1-microsoft-standard-WSL2 |
| CPUs | 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (8 x 1804) |
| Memory (System) | 7.62GB (5.72GB free) |
| VM | 0% |
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
f6dab269:30613381
a9j8j154:30646983
showlangstatbar:30737416
962ge761:30841074
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
copilotsettingc:30839828
synctok:30821570
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
dsvsc015cf:30829746
Metadata
Metadata
Assignees
Labels
experimentingFeature is part of an experimentFeature is part of an experimenttriage-neededNeeds assignment to the proper sub-teamNeeds assignment to the proper sub-team



Activity
karrtikr commentedon Sep 21, 2023
Hi Elad Avron (@eladavron) thanks for reaching out 👋 Please provide the debug logs which can help diagnose the issue:
Developer: Set log levelcommandPython-> SelectTraceDeveloper: Reload WindowcommandOutput for
Pythonin theOutputpanel (View→Output, change the drop-down the upper-right of theOutputpanel toPython)karrtikr commentedon Sep 25, 2023
Dup of #22056, this information would still be helpful there.
eladavron commentedon Sep 26, 2023
Hi, for some reason this issue stopped occurring for me.
karrtikr commentedon Sep 26, 2023
The issue was fixed with #22056 (comment) in pre-release 🙂 thanks for letting us know about this.