quite similar to a standard IPython session, with the difference that you can edit cells in-place multiple times until you obtain the desired results, rather than having to rerun separate scripts with the generate the literal $ symbol. 3.4.2 Headings You can add headings by starting a line with one (or multiple) # followed by a space, as in the following example: # Heading 1 # Heading 2 ## Heading 2.1 ## notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel. This opens the door for

quite similar to a standard IPython session, with the difference that you can edit cells in-place multiple times until you obtain the desired results, rather than having to rerun separate scripts with the generate the literal $ symbol. 3.4.2 Headings You can add headings by starting a line with one (or multiple) # followed by a space, as in the following example: # Heading 1 # Heading 2 ## Heading 2.1 ## notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel. This opens the door for

quite similar to a standard IPython session, with the difference that you can edit cells in-place multiple times until you obtain the desired results, rather than having to rerun separate scripts with the generate the literal $ symbol. 3.4.2 Headings You can add headings by starting a line with one (or multiple) # followed by a space, as in the following example: # Heading 1 # Heading 2 ## Heading 2.1 ## notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel. This opens the door for

quite similar to a standard IPython session, with the difference that you can edit cells in-place multiple times until you obtain the desired results, rather than having to rerun separate scripts with the generate the literal $ symbol. 3.4.2 Headings You can add headings by starting a line with one (or multiple) # followed by a space, as in the following example: # Heading 1 # Heading 2 ## Heading 2.1 ## notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel. This opens the door for

quite similar to a standard IPython session, with the difference that you can edit cells in-place multiple times until you obtain the desired results, rather than having to rerun separate scripts with the generate the literal $ symbol. 3.4.2 Headings You can add headings by starting a line with one (or multiple) # followed by a space, as in the following example: # Heading 1 # Heading 2 ## Heading 2.1 ## notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel. This opens the door for

quite similar to a standard IPython session, with the difference that you can edit cells in-place multiple times until you obtain the desired results, rather than having to rerun separate scripts with the generate the literal $ symbol. 3.4.2 Headings You can add headings by starting a line with one (or multiple) # followed by a space, as in the following example: # Heading 1 # Heading 2 ## Heading 2.1 ## notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel. This opens the door for

quite similar to a standard IPython session, with the difference that you can edit cells in-place multiple times until you obtain the desired results, rather than having to rerun separate scripts with the generate the literal $ symbol. 3.4.2 Headings You can add headings by starting a line with one (or multiple) # followed by a space, as in the following example: # Heading 1 # Heading 2 ## Heading 2.1 ## notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel. This opens the door for

quite similar to a standard IPython session, with the difference that you can edit cells in-place multiple times until you obtain the desired results, rather than having to rerun separate scripts with the generate the literal $ symbol. 3.4.2 Headings You can add headings by starting a line with one (or multiple) # followed by a space, as in the following example: # Heading 1 # Heading 2 ## Heading 2.1 ## notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel. This opens the door for

quite similar to a standard IPython session, with the difference that you can edit cells in-place multiple times until you obtain the desired results, rather than having to rerun separate scripts with the generate the literal $ symbol. 3.4.2 Headings You can add headings by starting a line with one (or multiple) # followed by a space, as in the following example: # Heading 1 # Heading 2 ## Heading 2.1 ## notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel. This opens the door for

quite similar to a standard IPython session, with the difference that you can edit cells in-place multiple times until you obtain the desired results, rather than having to rerun separate scripts with the generate the literal $ symbol. 3.4.2 Headings You can add headings by starting a line with one (or multiple) # followed by a space, as in the following example: # Heading 1 # Heading 2 ## Heading 2.1 ## notebook) The Kernel and Frontend communicate over a ZeroMQ/JSON based messaging protocol, which allows multiple Fron- tends (even of different types) to communicate with a single Kernel. This opens the door for