as additional text that accompanies the code but is not meant for execution. In this way, notebook files can serve as a complete computational record of a session, interleaving executable code with explanatory mathematics, and rich representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled clicking on their name. You can also drag and drop .ipynb notebooks and standard .py Python source code files into the notebook list area. When starting a notebook server from the command line, you can also

as additional text that accompanies the code but is not meant for execution. In this way, notebook files can serve as a complete computational record of a session, interleaving executable code with explanatory representations of resulting objects. These documents are internally JSON [http://en.wikipedia.org/wiki/JSON] files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled clicking on their name. You can also drag and drop .ipynb notebooks and standard .py Python source code files into the notebook list area. When starting a notebook server from the command line, you can also

as additional text that accompanies the code but is not meant for execution. In this way, notebook files can serve as a complete computational record of a session, interleaving executable code with explanatory mathematics, and rich representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled clicking on their name. You can also drag and drop .ipynb notebooks and standard .py Python source code files into the notebook list area. When starting a notebook server from the command line, you can also

as additional text that accompanies the code but is not meant for execution. In this way, notebook files can serve as a complete computational record of a session, interleaving executable code with explanatory representations of resulting objects. These documents are internally JSON [http://en.wikipedia.org/wiki/JSON] files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled clicking on their name. You can also drag and drop .ipynb notebooks and standard .py Python source code files into the notebook list area. When starting a notebook server from the command line, you can also

as additional text that accompanies the code but is not meant for execution. In this way, notebook files can serve as a complete computational record of a session, interleaving executable code with explanatory mathematics, and rich representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled clicking on their name. You can also drag and drop .ipynb notebooks and standard .py Python source code files into the notebook list area. When starting a notebook server from the command line, you can also

as additional text that accompanies the code but is not meant for execution. In this way, notebook files can serve as a complete computational record of a session, interleaving executable code with explanatory representations of resulting objects. These documents are internally JSON [http://en.wikipedia.org/wiki/JSON] files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled clicking on their name. You can also drag and drop .ipynb notebooks and standard .py Python source code files into the notebook list area. When starting a notebook server from the command line, you can also

as additional text that accompanies the code but is not meant for execution. In this way, notebook files can serve as a complete computational record of a session, interleaving executable code with explanatory mathematics, and rich representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled clicking on their name. You can also drag and drop .ipynb notebooks and standard .py Python source code files into the notebook list area. When starting a notebook server from the command line, you can also

as additional text that accompanies the code but is not meant for execution. In this way, notebook files can serve as a complete computational record of a session, interleaving executable code with explanatory mathematics, and rich representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled clicking on their name. You can also drag and drop .ipynb notebooks and standard .py Python source code files into the notebook list area. When starting a notebook server from the command line, you can also

as additional text that accompanies the code but is not meant for execution. In this way, notebook files can serve as a complete computational record of a session, interleaving executable code with explanatory mathematics, and rich representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled clicking on their name. You can also drag and drop .ipynb notebooks and standard .py Python source code files into the notebook list area. When starting a notebook server from the command line, you can also

as additional text that accompanies the code but is not meant for execution. In this way, notebook files can serve as a complete computational record of a session, interleaving executable code with explanatory mathematics, and rich representations of resulting objects. These documents are internally JSON files and are saved with the .ipynb extension. Since JSON is a plain text format, they can be version-controlled clicking on their name. You can also drag and drop .ipynb notebooks and standard .py Python source code files into the notebook list area. When starting a notebook server from the command line, you can also