publication-quality figures rendered by the matplotlib [http://matplotlib.org] library, can be included inline. In-browser editing for rich text using the Markdown [http://daringfireball.net/projects/markdown/syntax] include mathematical notation within markdown cells using LaTeX, and rendered natively by MathJax [http://www.mathjax.org/]. Notebook documents Notebook documents contains the inputs and outputs of a mathematics, and rich 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

publication-quality figures rendered by the matplotlib [http://matplotlib.org] library, can be included inline. In-browser editing for rich text using the Markdown [http://daringfireball.net/projects/markdown/syntax] include mathematical notation within markdown cells using LaTeX, and rendered natively by MathJax [http://www.mathjax.org/]. Notebook documents Notebook documents contains the inputs and outputs of a mathematics, and rich 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

publication-quality figures rendered by the matplotlib [http://matplotlib.org] library, can be included inline. In-browser editing for rich text using the Markdown [http://daringfireball.net/projects/markdown/syntax] include mathematical notation within markdown cells using LaTeX, and rendered natively by MathJax [http://www.mathjax.org/]. Notebook documents Notebook documents contains the inputs and outputs of a mathematics, and rich 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

as HTML, LaTeX, PNG, SVG, etc. For example, publication-quality figures rendered by the matplotlib [http://matplotlib.org] library, can be included inline. In-browser editing for rich text using the Markdown notebook document available from a public URL can be shared via the Jupyter Notebook Viewer (nbviewer [http://nbviewer.jupyter.org]). This service loads the notebook document from the URL and renders it as post, without other users needing to install the Jupyter notebook themselves. In effect, nbviewer [http://nbviewer.jupyter.org] is simply nbconvert [https://nbconvert.readthedocs.io/en/latest/] as a web

Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. Jupyter doesn’t send your data anywhere notebook server in your console, and open a web browser to the URL of the web application (by default, http://127.0.0.1:8888). The landing page of the Jupyter notebook web application, the dashboard, shows Apr%20milestone%3A5.5] involved in this release. 5.4.1 A security release to fix CVE-2018-8768 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE- 2018-8768]. Thanks to Alex [https://hackerone.com/pisarenko]

Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. Jupyter doesn’t send your data anywhere notebook server in your console, and open a web browser to the URL of the web application (by default, http://127.0.0.1:8888). The landing page of the Jupyter notebook web application, the dashboard, shows in this section are all converted notebook files. You can also view these notebooks on nbviewer [http://nbviewer.jupyter.org/github/jupyter/notebook/blob/master/docs/source/examples/Notebook/]. What

Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. Jupyter doesn’t send your data anywhere notebook server in your console, and open a web browser to the URL of the web application (by default, http://127.0.0.1:8888). The landing page of the Jupyter notebook web application, the dashboard, shows in this section are all converted notebook files. You can also view these notebooks on nbviewer [http://nbviewer.jupyter.org/github/jupyter/notebook/blob/master/docs/source/examples/Notebook/]. What

Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. Jupyter doesn’t send your data anywhere notebook server in your console, and open a web browser to the URL of the web application (by default, http://127.0.0.1:8888). The landing page of the Jupyter notebook web application, the dashboard, shows pr%20milestone%3A5.5] involved in this release. 5.4.1 A security release to fix CVE-2018-8768 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE- 2018-8768]. Thanks to Alex [https://hackerone.com/pisarenko]

Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. Jupyter doesn’t send your data anywhere notebook server in your console, and open a web browser to the URL of the web application (by default, http://127.0.0.1:8888). The landing page of the Jupyter notebook web application, the dashboard, shows Apr%20milestone%3A5.5] involved in this release. 5.4.1 A security release to fix CVE-2018-8768 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE- 2018-8768]. Thanks to Alex [https://hackerone.com/pisarenko]

Jupyter is actually running on your own computer. If the URL in the address bar starts with http://localhost: or http://127.0.0.1:, it’s your computer acting as the server. Jupyter doesn’t send your data anywhere notebook server in your console, and open a web browser to the URL of the web application (by default, http://127.0.0.1:8888). The landing page of the Jupyter notebook web application, the dashboard, shows Apr%20milestone%3A5.5] involved in this release. 5.4.1 A security release to fix CVE-2018-8768 [http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE- 2018-8768]. Thanks to Alex [https://hackerone.com/pisarenko]