Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
However, the consensus is that building official support for this would encourage creating notebooks that are JupyterLab specific and wouldn't be able to be supported by other frontends like nteract. The recommended approach is to create an extension, if you want to access the jupyterlab API.
In this case, it could possibly be an extension that handles a new mimetype by creating a new window for it and language specific wrappers that wrap outputs in this new mimetype. That would be easier for other frontends to also handle.
It would be good to document this rationale somewhere, maybe in the larger context of what features should be built into core vs what are better suited to third party extensions (at least at first).
EDIT: I am collecting issues that I think are related to this question of kernel execution being dependent on the frontend here:
Speaking as a developer on nteract and having fresh in mind why people elected building new APIs and UIs for jupyter, the reason you don't want your JS API exposed in outputs is for your own sanity. Someday you're going to want to change an API and you will be locked into past decisions or have to go the route of breaking things.
On Wed, May 23, 2018 at 12:26 PM, Kyle Kelley ***@***.***> wrote: Speaking as a developer on nteract and having fresh in mind *why* people elected building new APIs and UIs for jupyter, the reason you don't want your JS API exposed in outputs is for your own sanity. Someday you're going to want to change an API and you will be locked into past decisions *or* have to go the route of breaking things. My opinion on the best way to handle this is to define metadata for the message spec for this. Note -- this use case is pretty similar to the proposal from @BoPeng <https://github.com/BoPeng> in #4550 <#4550> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#4623 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABr0AkzKptQnPaFQ3Z3d4V_UN3XRDJvks5t1bfagaJpZM4UK0jT> .
-- Brian E. Granger Associate Professor of Physics and Data Science Cal Poly State University, San Luis Obispo @ellisonbg on Twitter and GitHub email@example.com and firstname.lastname@example.org