Review default kernel for Interactive Window

[DonJayamanne]

Today when run a cell in IW, we have the following logic:

• if we don't have remotes, then always use local active python env
• If we have a remote, use a kernel from remote (what' is used, not very clear)
• If we have more than one remote, what do we do

Should we instead force the user to pick a kernel?

[DonJayamanne]

Lets discuss this

[rebornix]

We can probably merge the later two into one: when there is a remote connected/used, ask users to pick a kernel first.

[DonJayamanne]

ere is a remote connected/used, ask users to pick a kernel first.

Agreed
For Notebooks, with the new Kernel Picker the user will always be prompted to select a kernel, irrespective of whether they are using local or remote kernels.

Prompting the user to select will be consistent.
Except for situations where they do not have a remote, in which case, we default back to local interpreter

Note: This will also impact the tests, today the tests are working, but its very hacky, the code use to select a kernel is very clunky and its basically just a lot of debt

[DonJayamanne]

Un-assigning myself as this change is related to IW.
@amunger let me know if there's anything you need from me