Steven Silvester

We discussed this at the in-person development meeting in June, and concluded for now that the notebook itself should remain single-language. Multi-language support could be achieved with a top level...

Hi @ndrewxie, I think 2.0 is probably a reasonable target. We are concentrating on getting feature parity with the classic notebook and ironing out the existing application for 1.0.

Hi @BoPeng, that is a tremendous achievement, congratulations and thank you for sharing it and starting a dialog. I would love to see a JupyterLab extension providing the SoS Notebook...

Hi @BoPeng, some thoughts after reading through the SoS documentation. - I think the [cell header](https://github.com/jupyterlab/jupyterlab/blob/26aa6a19507d124d6d3b2f3b63de0df50c7b8698/packages/cells/src/headerfooter.ts#L33) would be a good fit for the kernel selector dropdown - I think the...

cc @ellisonbg @Carreau @takluyver

cc @jasongrout

The current UX in JupyterLab 2.0 is the following: See discussion in https://github.com/jupyter/jupyter_server/issues/197 about a long term solution, but I think at the very least we should show a busy...

cc @tgeorgeux for UX input, thanks @mlucool!

It looks like this can't be cleanly backported, due to lifecycle differences at startup between 1.x and 2.x.

Hi @RampageousRJ, if you're still facing this issue, I'd suggest trying the solutions mentioned here: https://stackoverflow.com/a/78928284