Local Kernel Spec is a dead end

[jrieken]

Testing #11963

• selected "Select Another Kernel > Local Kernel Spec"
• I see an empty QP with nothing

I honest don't really know "Local Kernel Spec" is all about but I'd suggest to (1) don't give me that option to begin with or (2) show a message why this is empty and how I can populate it

[DonJayamanne]

show a message why this is empty and how I can populate it

should add an item with an information link as suggested my @amunger

[roblourens]

we need to be consistent, either always show or always hide. not show/hide dynamically at different points in time.

Is that not exactly what we are doing with the kernel picker now, as kernels get lazily discovered and loaded into the picker? I don't see the problem.

re: an info link, are kernel specs a really useful feature that we want to educate users on? If not, then why add a link on how to add kernel specs? I would expect that a user who needs to create kernel specs already understands this functionality.

[DonJayamanne]

Is that not exactly what we are doing with the kernel picker now, as kernels get lazily discovered and loaded into the picker? I don't see the problem.

If we wait for kernel to be discovered, then lazy loading is pointless (and will be slower to display this item)
today we register the Selct a Local Kernle Spec entry with vscode as soon as the extwension activates

[DonJayamanne]

Solution: Display this item only when we have discovered local kernelspecs