Yes, I can. But it seems that there is already a same issue in jupyter/notebook project (https://github.com/jupyter/notebook/issues/3170), I understand jupyterlab is using the jupyter/notebook as its backend, or jupyterlab will rewrite not only the frontend but also the backend ?
On Wednesday, May 1, 2019 at 6:48:29 AM UTC+8, Jason Grout wrote: > > On Tue, Apr 30, 2019 at 4:36 PM Song Liu <[email protected] <javascript:>> > wrote: > >> Yes, this is the kernel and Jupyter Server separation solution for my >> requirement. >> >> So what is the schedule for this kernel launching behavior change ? where >> could access this kind of discussion ? >> >> > The current state is: > > 1. We discussed this when implementing JupyterLab, and decided to go with > the classic notebook behavior for compatibility. > 2. We are releasing 1.0 shortly (in the next several months?), and we > (most likely) wouldn't change this behavior at this point for 1.0. > 3. We can take up this discussion after releasing 1.0, especially if > someone volunteers to do the work for it. > > Do you want to open an issue for "Launch a kernel for notebook only when > needed, not at open" in the jupyterlab repo at > https://github.com/jupyterlab/jupyterlab/issues/new? That will help us > keep track of this request. > > Thanks, > > Jason > > > > -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/d829a562-14eb-4292-b723-36a70936d5f7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
