When choosing the python interpreter for a python .py file we have the "browse" option to choose the interpreter:
But when choosing the Kernel for a notebook we don't
It rely on environments extension that may fail to detect all the available environments properly, specially on multi project workspaces with the .venvs on subfolders or out of workspace venvs, so we can not choose them manually for the notebooks.
So having an equivalent "browse" option on the kernel selector would be great as by now getting it to choose the right one implies tricking the environment manager plugin by opening a .py file choosing manually the desired one and then go to the notebook to choose it for each notebook and environment.
As the feature itself is already present on the .py interpreter selector from environments extension it should not imply a complex addition to reuse or replicate it on the notebooks kernel selector.
When choosing the python interpreter for a python
.pyfile we have the "browse" option to choose the interpreter:But when choosing the Kernel for a notebook we don't
It rely on environments extension that may fail to detect all the available environments properly, specially on multi project workspaces with the .venvs on subfolders or out of workspace venvs, so we can not choose them manually for the notebooks.
So having an equivalent "browse" option on the kernel selector would be great as by now getting it to choose the right one implies tricking the environment manager plugin by opening a
.pyfile choosing manually the desired one and then go to the notebook to choose it for each notebook and environment.As the feature itself is already present on the
.pyinterpreter selector from environments extension it should not imply a complex addition to reuse or replicate it on the notebooks kernel selector.