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
{{ message }}
Repository navigation
Add ignoreFocusOut setting for "Select Interpreter" Quick Pick #25703
The "Select Interpreter" Quick Pick provided by the vscode-python extension behaves differently from native VS Code Quick Pick (e.g., Command Palette, Go to File). In native Quick Pick, clicking outside the dropdown dismisses it. In the Python extension, the dropdown cannot be dismissed with mouse-only actions — the only options are selecting an interpreter or pressing Esc.
Discussion
The Python extension may have specific reasons for overriding this behavior (e.g., to prevent accidental dismissal).
However, this creates inconsistency and accessibility concerns, especially for users who are not easy to switch between mouse/keyboard operations.
Accessibility Impact
Users who cannot easily use the keyboard (e.g., some people with disabilities) are forced to select an interpreter even if they only wanted to cancel.
This increases cognitive and operational burden compared to native Quick Pick behavior.
Suggestion
Align the Python extension’s Quick Pick with VS Code’s native behavior by default (dismiss on focus out).
If the current design is intentional, consider adding a setting such as:
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Activity
eleanorjboyd commentedon Jan 5, 2026
will investigate this and why it isn't behaving how we expect - thanks for pointing this out! code pointer: https://github.com/microsoft/vscode/blob/ad1a84f1221323de613b1fbf1690a7680b2a0c61/src/vs/platform/quickinput/common/quickInput.ts#L351-L354
github-actions commentedon Feb 5, 2026
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Happy Coding!