Skip to content

No way to "Clear Workspace Interpreter Setting" #21850

Closed

Description

@djbrown

Type: Bug

Behaviour

Expected vs. Actual

I cannot reset the currently active workspace interpreter, even though this feature/command/setting is referred to on various issues (#18255, #17693, #17890, #17693, ...) and even in code:

Steps to reproduce:

  1. open command palette
  2. search for "python interpreter"
  3. expected command not list

Animation

Diagnostic data

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

XXX

User Settings


languageServer: "Pylance"

Extension version: 2023.14.0
VS Code version: Code 1.81.1 (6c3e3dba23e8fadc360aed75ce363ba185c49794, 2023-08-09T22:22:42.175Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 5.15.90.1-microsoft-standard-WSL2

System Info
Item Value
CPUs Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2592)
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
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Load (avg) undefined
Memory (System) 15.84GB (5.28GB free)
Process Argv --crash-reporter-id 6a947b0b-2920-480a-98a0-5c6d6b7ebd8c
Screen Reader no
VM 0%
Item Value
Remote WSL: Ubuntu
OS Linux x64 5.15.90.1-microsoft-standard-WSL2
CPUs Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2591)
Memory (System) 7.76GB (6.60GB free)
VM 0%
A/B Experiments
vsliv368:30146709
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
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263cf:30792227
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30803845
3biah626:30602489
f6dab269:30613381
vscrpc:30673769
showlangstatbar:30737416
03d35959:30757346
7ij38806:30736111
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofb:30804716
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
dsvsc013:30795093
dsvsc014:30804076
diffeditorv1:30812748

Activity

  1. djbrown commented on Aug 19, 2023

    @djbrown
    Author

    Possible workaround might be via usernamehw.commands as mentioned in #17693 (comment)
    Didn't look into that yet

  2. karrtikr commented on Aug 21, 2023

    @karrtikr

    Hi Daniel Brown (@djbrown) , we currently only show it if a Python file is currently opened, as that is when the currently selected interpreter is visible in the status bar:
    image

    Thanks for letting us know about this, we should probably clarify it in the docs.

  3. added
    debtCode quality issues
    area-environmentsFeatures relating to handling interpreter environments
    needs PRReady to be worked on
    and removed
    info-neededIssue requires more information from poster
    triage-neededNeeds assignment to the proper sub-team
    on Aug 21, 2023
  4. karrtikr commented on Aug 21, 2023

    @karrtikr

    Fix should be out in the pre-release version of the extension in a day, use the following to try it out:

    image

    I've changed it to always show the command even when a Python file isn't opened.

  5. djbrown commented on Aug 24, 2023

    @djbrown
    Author

    ahh when I have a python file open as current file then the command shows

    but switching to the pre-release version did not change the behaviour for me (command still only available if currentLanguae is python).

    but then agein I'm confused by the different version numbers:

    • in your screenshot it says v2022.3.2030538168-dev
    • on the marketplace page (web, IDE, GitHub) it says v2023.14.0
    • and after I switch to pre-release in VS Code the extension page says 2023.15.12301911

    Kartik Raj (@karrtikr) how can I check if I have the proper correct beta version of the plugin installed?

  6. djbrown commented on Aug 24, 2023

    @djbrown
    Author

    reloading or even restarting the IDE didn't help

  7. karrtikr commented on Aug 24, 2023

    @karrtikr

    Apologies, fix is actually only out in VS Code Insiders for now, can you try it out?

    image

    It should be out in the next official release of VS Code stable, which is around the 6th next month.

  8. djbrown commented on Aug 25, 2023

    @djbrown
    Author

    👍🏾 works on vscode-insiders extension prerelease version v2023.15.12361009

  9. locked as resolved and limited conversation to collaborators on Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

area-environmentsFeatures relating to handling interpreter environmentsdebtCode quality issuesverifiedVerification succeeded

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions