![]() Some extensions were “grand-fathered” in as core services to make the notebook application more full-featured (e.g. ![]() However, it isn’t clear what should be a core service versus a server extension. The old notebook server was comprised of many services, and it could be extended by separate “server extensions”. The server-notebook split is an opportunity to clearly define Jupyter’s core services. (This section needs a lot more discussion.) Preliminary work resides in jupyter_server.Ĭlearly define the smallest unit that is a “Jupyter Server” ¶ I18n: module for internationalizing the jupyter server Kernelspec: handler for getting kernelspec Services module: all jupyter server services, managers, and handlersīundler: handlers for building download bundlesįiles: handlers for serving files from contents manager. Tree module: a classic notebook file browser+handlers. Static directory: all js and style sheets for notebook frontend. View module: handlers for file viewer component. Terminal module: handlers for the classic notebook terminal application. Templates directory: all html templates for the classic notebook These pieces will stay in the notebook repository.Įdit module: the handlers for the classic notebook text editor. Tornado handlers to the classic notebook interface. A new jupyter_server repo will keep the server specific logic and remove: Namespacing static files and REST API urls.Įach extension serves static files at the /static/ url. Jupyter_notebook_config.d folder becomes jupyter_server_config.d New base classes to create applications from server extensions. Server extensions move to jupyter_server. Kernel, KernelSpecs, and Session (?) become the only core servicesĮverything else becomes a server extension? Notebook tornado handlers and frontend logic stay in notebook repo.ĭeprecated notebook server APIs do not move to jupyter_server.Ĭlearly define the smallest unit that is a “Jupyter Server” Pure Python package with notebook backend services. Decouple the backend server (and its configuration) from the classic notebook frontend. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |