Stop hiding default Python kernelspecs in kernel picker #16953
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change removes the logic that was hiding default Python kernelspecs (like
python3
,python
,Python 3 (ipykernel)
) from the kernel picker.Problem:
Users were filing issues because they couldn't find kernelspecs they expected to see, leading them to believe the Jupyter extension wasn't working properly. The extension was automatically hiding default Python kernelspecs when:
Solution:
The original rationale for hiding these kernelspecs was to avoid user confusion between Python environments and kernelspecs. However, this reasoning no longer applies since the kernel picker now has separate sections for "Python Environments" and "Jupyter Kernels", making the distinction clear to users.
Changes:
InterpreterSpecificKernelSpecsFinder.listKernelSpecsImpl()
Impact:
Default Python kernelspecs will now appear in the kernel picker alongside custom kernelspecs, improving discoverability and reducing user confusion about missing kernels.
Fixes #15557.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.