Show More
@@ -53,4 +53,19 b' the target language:' | |||
|
53 | 53 | |
|
54 | 54 | :doc:`wrapperkernels` |
|
55 | 55 | |
|
56 | ||
|
56 | Notebooks | |
|
57 | --------- | |
|
58 | ||
|
59 | The Notebook frontend does something extra. In addition to running your code, it | |
|
60 | stores code and output, together with markdown notes, in an editable document | |
|
61 | called a notebook. When you save it, this is sent from your browser to the | |
|
62 | notebook server, which saves it on disk as a JSON file with a ``.ipynb`` | |
|
63 | extension. | |
|
64 | ||
|
65 | .. TODO: Diagram of how these pieces fit together. | |
|
66 | ||
|
67 | The notebook server, not the kernel, is responsible for saving and loading | |
|
68 | notebooks, so you can edit notebooks even if you don't have the kernel for that | |
|
69 | language—you just won't be able to run code. The kernel doesn't know anything | |
|
70 | about the notebook document: it just gets sent cells of code to execute when the | |
|
71 | user runs them. |
General Comments 0
You need to be logged in to leave comments.
Login now