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 and shared with static conversions with nbconvert, without relying on nbviewer. See also: Details on the notebook JSON file format 1.1.3 Notebooks and privacy Because you use Jupyter in a web browser, some people are notebook. Each of these kernels communicate with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about

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 and shared with static conversions with nbconvert, without relying on nbviewer. See also: Details on the notebook JSON file format 1.1.3 Notebooks and privacy Because you use Jupyter in a web browser, some people are notebook. Each of these kernels communicate with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about

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 and shared with static conversions with nbconvert, without relying on nbviewer. See also: Details on the notebook JSON file format 1.1.3 Notebooks and privacy Because you use Jupyter in a web browser, some people are notebook. Each of these kernels communicate with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about

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 and shared with static conversions with nbconvert, without relying on nbviewer. See also: Details on the notebook JSON file format 1.1.3 Notebooks and privacy Because you use Jupyter in a web browser, some people are notebook. Each of these kernels communicate with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about

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 and shared with static conversions with nbconvert, without relying on nbviewer. See also: Details on the notebook JSON file format 1.1.3 Notebooks and privacy Because you use Jupyter in a web browser, some people are notebook. Each of these kernels communicate with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about

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 and shared with static conversions with nbconvert, without relying on nbviewer. See also: Details on the notebook JSON file format 1.1.3 Notebooks and privacy Because you use Jupyter in a web browser, some people are notebook. Each of these kernels communicate with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about

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 and shared with static conversions with nbconvert, without relying on nbviewer. See also: Details on the notebook JSON file format 1.1.3 Notebooks and privacy Because you use Jupyter in a web browser, some people are notebook. Each of these kernels communicate with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about

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 and shared with static conversions with nbconvert, without relying on nbviewer. See also: Details on the notebook JSON file format 1.1.3 Notebooks and privacy Because you use Jupyter in a web browser, some people are notebook. Each of these kernels communicate with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about

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 and shared with static conversions with nbconvert, without relying on nbviewer. See also: Details on the notebook JSON file format 1.1.3 Notebooks and privacy Because you use Jupyter in a web browser, some people are notebook. Each of these kernels communicate with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about

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 and shared with static conversions with nbconvert, without relying on nbviewer. See also: Details on the notebook JSON file format 1.1.3 Notebooks and privacy Because you use Jupyter in a web browser, some people are notebook. Each of these kernels communicate with the notebook web application and web browser using a JSON over Ze- roMQ/WebSockets message protocol that is described here. Most users don’t need to know about