the notebook to open a Qt console connected to the same kernel. See also: Decoupled two-process model 1.3 Notebook user interface When you create a new notebook document, you will be presented with once we figure out the filename of the module, all it does is: 1. load the notebook document into memory 2. create an empty Module 3. execute every cell in the Module namespace Since IPython cells can magic. 3.9 Connecting to an existing IPython kernel using the Qt Console 3.9.1 The Frontend/Kernel Model The traditional IPython (ipython) consists of a single process that combines a terminal based UI

the notebook to open a Qt console connected to the same kernel. See also: Decoupled two-process model 1.3 Notebook user interface When you create a new notebook document, you will be presented with once we figure out the filename of the module, all it does is: 1. load the notebook document into memory 2. create an empty Module 3. execute every cell in the Module namespace Since IPython cells can magic. 3.9 Connecting to an existing IPython kernel using the Qt Console 3.9.1 The Frontend/Kernel Model The traditional IPython (ipython) consists of a single process that combines a terminal based UI

the notebook to open a Qt console connected to the same kernel. See also: Decoupled two-process model 1.3 Notebook user interface When you create a new notebook document, you will be presented with once we figure out the filename of the module, all it does is: 1. load the notebook document into memory 2. create an empty Module 3. execute every cell in the Module namespace Since IPython cells can magic. 3.9 Connecting to an existing IPython kernel using the Qt Console 3.9.1 The Frontend/Kernel Model The traditional IPython (ipython) consists of a single process that combines a terminal based UI

the notebook to open a Qt console connected to the same kernel. See also: Decoupled two-process model 1.3 Notebook user interface When you create a new notebook document, you will be presented with once we figure out the filename of the module, all it does is: 1. load the notebook document into memory 2. create an empty Module 3. execute every cell in the Module namespace Since IPython cells can magic. 3.9 Connecting to an existing IPython kernel using the Qt Console 3.9.1 The Frontend/Kernel Model The traditional IPython (ipython) consists of a single process that combines a terminal based UI

the notebook to open a Qt console connected to the same kernel. See also: Decoupled two-process model 1.3 Notebook user interface When you create a new notebook document, you will be presented with once we figure out the filename of the module, all it does is: 1. load the notebook document into memory 2. create an empty Module 3. execute every cell in the Module namespace Since IPython cells can magic. 3.9 Connecting to an existing IPython kernel using the Qt Console 3.9.1 The Frontend/Kernel Model The traditional IPython (ipython) consists of a single process that combines a terminal based UI

the notebook to open a Qt console connected to the same kernel. See also: Decoupled two-process model 1.3 Notebook user interface When you create a new notebook document, you will be presented with once we figure out the filename of the module, all it does is: 1. load the notebook document into memory 2. create an empty Module 3. execute every cell in the Module namespace Since IPython cells can magic. 3.9 Connecting to an existing IPython kernel using the Qt Console 3.9.1 The Frontend/Kernel Model The traditional IPython (ipython) consists of a single process that combines a terminal based UI

the notebook to open a Qt console connected to the same kernel. See also: Decoupled two-process model 1.3 Notebook user interface When you create a new notebook document, you will be presented with once we figure out the filename of the module, all it does is: 1. load the notebook document into memory 2. create an empty Module 3. execute every cell in the Module namespace Since IPython cells can magic. 3.9 Connecting to an existing IPython kernel using the Qt Console 3.9.1 The Frontend/Kernel Model The traditional IPython (ipython) consists of a single process that combines a terminal based UI

the notebook to open a Qt console connected to the same kernel. See also: Decoupled two-process model 1.3 Notebook user interface When you create a new notebook document, you will be presented with once we figure out the filename of the module, all it does is: 1. load the notebook document into memory 2. create an empty Module 3. execute every cell in the Module namespace Since IPython cells can magic. 3.9 Connecting to an existing IPython kernel using the Qt Console 3.9.1 The Frontend/Kernel Model The traditional IPython (ipython) consists of a single process that combines a terminal based UI

the notebook to open a Qt console connected to the same kernel. See also: Decoupled two-process model 1.3 Notebook user interface When you create a new notebook document, you will be presented with once we figure out the filename of the module, all it does is: 1. load the notebook document into memory 2. create an empty Module 3. execute every cell in the Module namespace Since IPython cells can magic. 3.9 Connecting to an existing IPython kernel using the Qt Console 3.9.1 The Frontend/Kernel Model The traditional IPython (ipython) consists of a single process that combines a terminal based UI

the notebook to open a Qt console connected to the same kernel. See also: Decoupled two-process model 1.3 Notebook user interface When you create a new notebook document, you will be presented with once we figure out the filename of the module, all it does is: 1. load the notebook document into memory 2. create an empty Module 3. execute every cell in the Module namespace Since IPython cells can magic. 3.9 Connecting to an existing IPython kernel using the Qt Console 3.9.1 The Frontend/Kernel Model The traditional IPython (ipython) consists of a single process that combines a terminal based UI