8000 Discovering Python interpreters takes a long time · Issue #19669 · microsoft/vscode-python · GitHub
[go: up one dir, main page]

Skip to content
Discovering Python interpreters takes a long time #19669
Closed as not planned
Closed as not planned
@minsa110

Description

@minsa110

Type: Bug

Behaviour

Expected vs. Actual

  1. Launch VS Code insiders after an update
  2. The "Discovering Python Interpreters" step takes a very long time (I didn't time it), so I don't see my Python environments in the Jupyter kernel picker for a while
  3. Close VS Code insiders
  4. Launch VS Code insiders again (no update this time)
  5. The "Discovering Python Interpreters" step also takes a very long time (~40 seconds for that operation alone), but since Python environments were already loaded from previous session, they still do show up in the Jupyter kernel picker

Diagnostic data

  • Python version (& distribution if applicable, e.g. Anaconda): 3.8.5
  • Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
  • Value of the python.languageServer setting: Default
Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings


languageServer: "Pylance"

Extension version: 2022.13.12212101
VS Code version: Code - Insiders 1.71.0-insider (dced70b, 2022-08-10T05:17:53.560Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: Yes

System Info
Item Value
CPUs Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1498)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: disabled_off
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
skia_renderer: enabled_on
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: disabled_off
Load (avg) undefined
Memory (System) 15.60GB (1.34GB free)
Process Argv --crash-reporter-id 7c55b80b-a2c8-4229-8934-3646319b9311
Screen Reader no
VM 0%
A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
pythonvspyt551cf:30291413
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30404738
wslgetstarted:30449409
cppdebug:30492333
pylanb8912:30522163
vsclangdf:30492506
c4g48928:30535728
dsvsc012:30540213

Metadata

Metadata

Assignees

Labels

area-environmentsFeatures relating to handling interpreter environmentsbugIssue identified by VS Code Team member as probable bugtriage-neededNeeds assignment to the proper sub-team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0