Merge pull request #7879 from minrk/rm-old-nbformat

remove old notebook format doc at the bottom of nbconvert doc

docs/source/notebook/nbconvert.rst

@@ -1,230 +1,139 b''
 .. _nbconvert:
 
 Converting notebooks to other formats
 =====================================
 
 Newly added in the 1.0 release of IPython is the ``nbconvert`` tool, which 
 allows you to convert an ``.ipynb`` notebook document file into various static 
 formats. 
 
 Currently, ``nbconvert`` is provided as a command line tool, run as a script 
 using IPython. A direct export capability from within the 
 IPython Notebook web app is planned. 
 
 The command-line syntax to run the ``nbconvert`` script is::
 
   $ ipython nbconvert --to FORMAT notebook.ipynb
 
 This will convert the IPython document file ``notebook.ipynb`` into the output 
 format given by the ``FORMAT`` string.
 
 The default output format is html, for which the ``--to`` argument may be 
 omitted::
   
   $ ipython nbconvert notebook.ipynb
 
 IPython provides a few templates for some output formats, and these can be
 specified via an additional ``--template`` argument.
 
 The currently supported export formats are:
 
 * ``--to html``
 
   - ``--template full`` (default)
   
     A full static HTML render of the notebook.
     This looks very similar to the interactive view.
 
   - ``--template basic``
   
     Simplified HTML, useful for embedding in webpages, blogs, etc.
     This excludes HTML headers.
 
 * ``--to latex``
 
   Latex export.  This generates ``NOTEBOOK_NAME.tex`` file,
   ready for export.  You can automatically run latex on it to generate a PDF
   by adding ``--post PDF``.
   
   - ``--template article`` (default)
   
     Latex article, derived from Sphinx's howto template.
 
   - ``--template book``
   
     Latex book, derived from Sphinx's manual template.
 
   - ``--template basic``
   
     Very basic latex output - mainly meant as a starting point for custom templates.
 
 * ``--to slides``
 
   This generates a Reveal.js HTML slideshow.
   It must be served by an HTTP server. The easiest way to do this is adding 
   ``--post serve`` on the command-line. The ``serve`` post-processor proxies 
   Reveal.js requests to a CDN if no local Reveal.js library is present.
   To make slides that don't require an internet connection, just place the 
   Reveal.js library in the same directory where your_talk.slides.html is located, 
   or point to another directory using the ``--reveal-prefix`` alias.
 
 * ``--to markdown``
 
   Simple markdown output.  Markdown cells are unaffected,
   and code cells indented 4 spaces.
 
 * ``--to rst``
 
   Basic reStructuredText output. Useful as a starting point for embedding notebooks
   in Sphinx docs.
 
 * ``--to python``
 
   Convert a notebook to an executable Python script.
   This is the simplest way to get a Python script out of a notebook.
   If there were any magics in the notebook, this may only be executable from
   an IPython session.
   
 .. note::
 
   nbconvert uses pandoc_ to convert between various markup languages,
   so pandoc is a dependency of most nbconvert transforms,
   excluding Markdown and Python.
 
 .. _pandoc: http://johnmacfarlane.net/pandoc/
 
 The output file created by ``nbconvert`` will have the same base name as
 the notebook and will be placed in the current working directory. Any
 supporting files (graphics, etc) will be placed in a new directory with the
 same base name as the notebook, suffixed with ``_files``::
 
   $ ipython nbconvert notebook.ipynb
   $ ls
   notebook.ipynb   notebook.html    notebook_files/
 
 For simple single-file output, such as html, markdown, etc.,
 the output may be sent to standard output with::
     
   $ ipython nbconvert --to markdown notebook.ipynb --stdout
     
 Multiple notebooks can be specified from the command line::
     
   $ ipython nbconvert notebook*.ipynb
   $ ipython nbconvert notebook1.ipynb notebook2.ipynb
     
 or via a list in a configuration file, say ``mycfg.py``, containing the text::
 
   c = get_config()
   c.NbConvertApp.notebooks = ["notebook1.ipynb", "notebook2.ipynb"]
 
 and using the command::
 
   $ ipython nbconvert --config mycfg.py
 
 
-.. _notebook_format:
-
 LaTeX citations
 ---------------
 
 ``nbconvert`` now has support for LaTeX citations. With this capability you
 can:
 
 * Manage citations using BibTeX.
 * Cite those citations in Markdown cells using HTML data attributes.
 * Have ``nbconvert`` generate proper LaTeX citations and run BibTeX.
 
 For an example of how this works, please see the citations example in
 the nbconvert-examples_ repository.
 
 .. _nbconvert-examples: https://github.com/ipython/nbconvert-examples
 
-Notebook JSON file format
--------------------------
-
-Notebook documents are JSON files with an ``.ipynb`` extension, formatted
-as legibly as possible with minimal extra indentation and cell content broken
-across lines to make them reasonably friendly to use in version-control
-workflows.  You should be very careful if you ever manually edit this JSON
-data, as it is extremely easy to corrupt its internal structure and make the
-file impossible to load.  In general, you should consider the notebook as a
-file meant only to be edited by the IPython Notebook app itself, not for 
-hand-editing.
-
-.. note::
-
-     Binary data such as figures are also saved directly in the JSON file.  
-     This provides convenient single-file portability, but means that the 
-     files can be large; a ``diff`` of binary data is also not very 
-     meaningful.  Since the binary blobs are encoded in a single line, they 
-     affect only one line of the ``diff`` output, but they are typically very 
-     long lines.  You can use the ``Cell | All Output | Clear`` menu option to 
-     remove all output from a notebook prior to committing it to version 
-     control, if this is a concern.
-
-The notebook server can also generate a pure Python version of your notebook, 
-using the ``File | Download as`` menu option. The resulting ``.py`` file will 
-contain all the code cells from your notebook verbatim, and all Markdown cells 
-prepended with a comment marker.  The separation between code and Markdown
-cells is indicated with special comments and there is a header indicating the
-format version.  All output is removed when exporting to Python.
-
-As an example, consider a simple notebook called ``simple.ipynb`` which 
-contains one Markdown cell, with the content ``The simplest notebook.``, one 
-code input cell with the content ``print "Hello, IPython!"``, and the 
-corresponding output.
-
-The contents of the notebook document ``simple.ipynb`` is the following JSON 
-container::
-
-  {
-   "metadata": {
-    "name": "simple"
-   },
-   "nbformat": 3,
-   "nbformat_minor": 0,
-   "worksheets": [
-    {
-     "cells": [
-      {
-       "cell_type": "markdown",
-       "metadata": {},
-       "source": "The simplest notebook."
-      },
-      {
-       "cell_type": "code",
-       "collapsed": false,
-       "input": "print \"Hello, IPython\"",
-       "language": "python",
-       "metadata": {},
-       "outputs": [
-        {
-         "output_type": "stream",
-         "stream": "stdout",
-         "text": "Hello, IPython\n"
-        }
-       ],
-       "prompt_number": 1
-      }
-     ],
-     "metadata": {}
-    }
-   ]
-  }
-
-
-The corresponding Python script is::
-
-  # -*- coding: utf-8 -*-
-  # <nbformat>3.0</nbformat>
-
-  # <markdowncell>
-
-  # The simplest notebook.
-
-  # <codecell>
-
-  print "Hello, IPython"
-
-Note that indeed the output of the code cell, which is present in the JSON 
-container, has been removed in the ``.py`` script.

docs/source/notebook/notebook.rst

@@ -1,482 +1,482 b''
 .. _htmlnotebook:
 
 The IPython Notebook
 ====================
 
 Introduction
 ------------
 
 The notebook extends the console-based approach to interactive computing in
 a qualitatively new direction, providing a web-based application suitable for
 capturing the whole computation process: developing, documenting, and
 executing code, as well as communicating the results.  The IPython notebook
 combines two components:
 
 **A web application**: a browser-based tool for interactive authoring of
 documents which combine explanatory text, mathematics, computations and their
 rich media output.
 
 **Notebook documents**: a representation of all content visible in the web
 application, including inputs and outputs of the computations, explanatory
 text, mathematics, images, and rich media representations of objects.
 
 .. seealso::
 
     See the :ref:`installation documentation <installnotebook>` for directions
     on how to install the notebook and its dependencies.
 
 
 Main features of the web application
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 * In-browser editing for code, with automatic syntax highlighting,
   indentation, and tab completion/introspection.
 
 * The ability to execute code from the browser, with the results of
   computations attached to the code which generated them.
 
 * Displaying the result of computation using rich media representations, such
   as HTML, LaTeX, PNG, SVG, etc. For example, publication-quality figures
   rendered by the matplotlib_ library, can be included inline.
 
 * In-browser editing for rich text using the Markdown_ markup language, which
   can provide commentary for the code, is not limited to plain text.
 
 * The ability to easily include mathematical notation within markdown cells
   using LaTeX, and rendered natively by MathJax_.
 
 
 
 .. _MathJax: http://www.mathjax.org/
 
 
 Notebook documents
 ~~~~~~~~~~~~~~~~~~
 Notebook documents contains the inputs and outputs of a interactive session as
 well 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 text,
 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 and shared with
 colleagues.  
    
 .. _JSON: http://en.wikipedia.org/wiki/JSON
 
 Notebooks may be exported to a range of static formats, including HTML (for
 example, for blog posts), reStructuredText, LaTeX, PDF, and slide shows, via
 the new :ref:`nbconvert <nbconvert>` command.
 
 Furthermore, any  ``.ipynb`` notebook document available from a public 
 URL can be shared via the `IPython Notebook Viewer <nbviewer>`_ (nbviewer_).
 This service loads the notebook document from the URL and renders it as a
 static web page.  The results may thus be shared with a colleague, or as a
 public blog post, without other users needing to install IPython themselves.
 In effect, nbviewer_ is simply :ref:`nbconvert <nbconvert>` as a web service,
 so you can do your own static conversions with nbconvert, without relying on
 nbviewer.
 
 
 
 .. seealso::
 
-    :ref:`Details on the notebook JSON file format <notebook_format>` 
+    :ref:`Details on the notebook JSON file format <nbformat>` 
    
 
 Starting the notebook server
 ----------------------------
 
 You can start running a notebook server from the command line using the
 following command::
 
     ipython notebook
 
 This will print some information about the 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 IPython notebook web application, the **dashboard**,
 shows the notebooks currently available in the notebook directory (by default,
 the directory from which the notebook server was started).
 
 You can create new notebooks from the dashboard with the ``New Notebook``
 button, or open existing ones by 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 open a
 particular notebook directly, bypassing the dashboard, with ``ipython notebook
 my_notebook.ipynb``. The ``.ipynb`` extension is assumed if no extension is
 given.
 
 When you are inside an open notebook, the `File | Open...` menu option will
 open the dashboard in a new browser tab, to allow you to open another notebook
 from the notebook directory or to create a new notebook.
 
 
 .. note::
 
    You can start more than one notebook server at the same time, if you want 
    to work on notebooks in different directories.  By default the first 
    notebook server starts on port 8888, and later notebook servers search for  
    ports near that one.  You can also manually specify the port with the 
    ``--port`` option.
 
 Creating a new notebook document
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 A new notebook may be created at any time, either from the dashboard, or using
 the `File | New` menu option from within an active notebook. The new notebook
 is created within the same directory and will open in a new browser tab. It
 will also be reflected as a new entry in the notebook list on the dashboard.
 
 
 Opening notebooks
 ~~~~~~~~~~~~~~~~~
 An open notebook has **exactly one** interactive session connected to an
 :ref:`IPython kernel <ipythonzmq>`, which will execute code sent by the user
 and communicate back results.  This kernel remains active if the web browser
 window is closed, and reopening the same notebook from the dashboard will
 reconnect the web application to the same kernel. In the dashboard, notebooks
 with an active kernel have a ``Shutdown`` button next to them, whereas
 notebooks without an active kernel have a ``Delete`` button in its place.
 
 Other clients may connect to the same underlying IPython kernel.
 The notebook server always prints to the terminal the full details of 
 how to connect to each kernel, with messages such as the following::
 
     [NotebookApp] Kernel started: 87f7d2c0-13e3-43df-8bb8-1bd37aaf3373
 
 This long string is the kernel's ID which is sufficient for getting the
 information necessary to connect to the kernel.  You can also request this
 connection data by running the ``%connect_info`` :ref:`magic
 <magics_explained>`. This will print the same ID information as well as the
 content of the JSON data structure it contains.
 
 You can then, for example, manually start a Qt console connected to the *same*
 kernel from the command line, by passing a portion of the ID::
 
     $ ipython qtconsole --existing 87f7d2c0
 
 Without an ID, ``--existing`` will  connect to the most recently 
 started kernel. This can also be done by running the ``%qtconsole``
 :ref:`magic <magics_explained>` in the notebook.
 
 .. seealso::
 
     :ref:`ipythonzmq`
 
 Notebook user interface
 -----------------------
 
 When you create a new notebook document, you will be presented with the
 **notebook name**, a **menu bar**, a **toolbar** and an empty **code
 cell**.
 
 **notebook name**: The name of the notebook document is displayed at the top
 of the page, next to the ``IP[y]: Notebook`` logo. This name reflects the name
 of the ``.ipynb`` notebook document file.  Clicking on the notebook name
 brings up a dialog which allows you to rename it. Thus, renaming a notebook
 from "Untitled0" to "My first notebook" in the browser, renames the
 ``Untitled0.ipynb`` file to ``My first notebook.ipynb``. 
 
 **menu bar**: The menu bar presents different options that may be used to
 manipulate the way the notebook functions.
 
 **toolbar**: The tool bar gives a quick way of performing the most-used
 operations within the notebook, by clicking on an icon.
 
 **code cell**: the default type of cell, read on for an explanation of cells
 
 
 Structure of a notebook document
 --------------------------------
 
 The notebook consists of a sequence of cells.  A cell is a multi-line
 text input field, and its contents can be executed by using
 :kbd:`Shift-Enter`, or by clicking either the "Play" button the toolbar, or
 `Cell | Run` in the menu bar.  The execution behavior of a cell is determined
 the cell's type.  There are four types of cells: **code cells**, **markdown
 cells**, **raw cells** and **heading cells**.  Every cell starts off
 being a **code cell**, but its type can be changed by using a dropdown on the
 toolbar (which will be "Code", initially), or via :ref:`keyboard shortcuts
 <keyboard-shortcuts>`.  
 
 For more information on the different things you can do in a notebook,
 see the `collection of examples
 <http://nbviewer.ipython.org/github/ipython/ipython/blob/master/examples/Notebook/Index.ipynb>`_.
 
 Code cells
 ~~~~~~~~~~
 A *code cell* allows you to edit and write new code, with full syntax
 highlighting and tab completion. By default, the language associated to a code
 cell is Python, but other languages, such as ``Julia`` and ``R``, can be
 handled using :ref:`cell magic commands <magics_explained>`.
 
 When a code cell is executed, code that it contains is sent to the kernel
 associated with the notebook.  The results that are returned from this 
 computation  are then displayed in the notebook as the cell's *output*. The
 output is not limited to text, with many other possible forms of output are
 also possible, including ``matplotlib`` figures and HTML tables (as used, for 
 example, in the ``pandas`` data analysis package). This is known as IPython's 
 *rich display* capability.
 
 .. seealso::
 
     `Basic Output`_  example notebook
 
     `Rich Display System`_  example notebook
 
 Markdown cells
 ~~~~~~~~~~~~~~
 You can document the computational process in a literate way, alternating 
 descriptive text with code, using *rich text*. In IPython this is accomplished 
 by marking up text with the Markdown language. The corresponding cells are 
 called *Markdown cells*. The Markdown language provides a simple way to 
 perform this text markup, that is, to specify which parts of the text should 
 be emphasized (italics), bold, form lists, etc. 
 
 
 When a Markdown cell is executed, the Markdown code is converted into 
 the corresponding formatted rich text. Markdown allows arbitrary HTML code for
 formatting.
 
 Within Markdown cells, you can also include *mathematics* in a straightforward 
 way, using standard LaTeX notation: ``$...$`` for inline mathematics and 
 ``$$...$$`` for displayed mathematics. When the Markdown cell is executed, 
 the LaTeX portions are automatically rendered in the HTML output as equations 
 with high quality typography. This is made possible by MathJax_, which 
 supports a `large subset <mathjax_tex>`_ of LaTeX functionality 
 
 .. _mathjax_tex: http://docs.mathjax.org/en/latest/tex.html
 
 Standard mathematics environments defined by LaTeX and AMS-LaTeX (the 
 `amsmath` package) also work, such as 
 ``\begin{equation}...\end{equation}``, and ``\begin{align}...\end{align}``.
 New LaTeX macros may be defined using standard methods, 
 such as ``\newcommand``, by placing them anywhere *between math delimiters* in 
 a Markdown cell. These definitions are then available throughout the rest of 
 the IPython session. 
 
 .. seealso::
 
     `Markdown Cells`_ example notebook
 
 Raw cells
 ~~~~~~~~~
 
 *Raw* cells provide a place in which you can write *output* directly.
 Raw cells are not evaluated by the notebook.
 When passed through :ref:`nbconvert <nbconvert>`, raw cells arrive in the
 destination format unmodified. For example, this allows you to type full LaTeX
 into a raw cell, which will only be rendered by LaTeX after conversion by
 nbconvert.
 
 Heading cells
 ~~~~~~~~~~~~~
 
 You can provide a conceptual structure for your computational document as a 
 whole using different levels of headings; there are 6 levels available, from 
 level 1 (top level) down to level 6 (paragraph). These can be used later for 
 constructing tables of contents, etc.  As with Markdown cells, a heading 
 cell is replaced by a rich text rendering of the heading when the cell is
 executed.
 
 
 Basic workflow
 --------------
 
 The normal workflow in a notebook is, then, 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 ``%run`` magic command. 
 
 
 Typically, you will work on a computational problem in pieces, organizing 
 related ideas into cells and moving forward once previous parts work 
 correctly. This is much more convenient for interactive exploration than 
 breaking up a computation into scripts that must be executed together, as was 
 previously necessary, especially if parts of them take a long time to run.
 
 At certain moments, it may be necessary to interrupt a calculation which is 
 taking too long to complete. This may be done with the `Kernel | Interrupt` 
 menu option, or the :kbd:`Ctrl-m i` keyboard shortcut.
 Similarly, it may be necessary or desirable to restart the whole computational 
 process, with the `Kernel | Restart` menu option or :kbd:`Ctrl-m .` 
 shortcut. 
 
 A notebook may be downloaded in either a ``.ipynb`` or ``.py`` file from the
 menu option `File | Download as`. Choosing the ``.py`` option downloads a
 Python ``.py`` script, in which all rich output has been removed and the
 content of markdown cells have been inserted as comments.  
 
 .. seealso::
 
     `Running Code in the IPython Notebook`_ example notebook
 
     `Basic Output`_ example notebook
 
     :ref:`a warning about doing "roundtrip" conversions <note_about_roundtrip>`.
 
 .. _keyboard-shortcuts:
 
 Keyboard shortcuts
 ~~~~~~~~~~~~~~~~~~
 All actions in the notebook can be performed with the mouse, but keyboard 
 shortcuts are also available for the most common ones. The essential shortcuts
 to remember are the following:
 
 * :kbd:`Shift-Enter`:  run cell
     Execute the current cell, show output (if any), and jump to the next cell 
     below. If :kbd:`Shift-Enter` is invoked on the last cell, a new code 
     cell will also be created. Note that in the notebook, typing :kbd:`Enter` 
     on its own *never* forces execution, but rather just inserts a new line in 
     the current cell. :kbd:`Shift-Enter` is equivalent to clicking the 
     ``Cell | Run`` menu item.
 
 * :kbd:`Ctrl-Enter`: run cell in-place
     Execute the current cell as if it were in "terminal mode", where any 
     output is shown, but the cursor *remains* in the current cell. The cell's
     entire contents are selected after execution, so you can just start typing
     and only the new input will be in the cell. This is convenient for doing
     quick experiments in place, or for querying things like filesystem
     content, without needing to create additional cells that you may not want
     to be saved in the notebook.
 
 * :kbd:`Alt-Enter`: run cell, insert below
     Executes the current cell, shows the output, and inserts a *new* 
     cell between the current cell and the cell below (if one exists). This  
     is thus a shortcut for the sequence :kbd:`Shift-Enter`, :kbd:`Ctrl-m a`.
     (:kbd:`Ctrl-m a` adds a new cell above the current one.)
   
 * :kbd:`Esc` and :kbd:`Enter`: Command mode and edit mode
     In command mode, you can easily navigate around the notebook using keyboard
     shortcuts. In edit mode, you can edit text in cells.
 
 For the full list of available shortcuts, click :guilabel:`Help`,
 :guilabel:`Keyboard Shortcuts` in the notebook menus.
 
 Plotting
 --------
 One major feature of the notebook is the ability to display plots that are the
 output of running code cells. IPython is designed to work seamlessly with the
 matplotlib_ plotting library to provide this functionality. 
 
 To set this up, before any plotting is performed you must execute the
 ``%matplotlib``  :ref:`magic command <magics_explained>`. This performs the
 necessary behind-the-scenes setup for IPython to work correctly hand in hand
 with ``matplotlib``; it does *not*, however, actually execute any Python
 ``import`` commands, that is, no names are added to the namespace.
 
 If the ``%matplotlib`` magic is called without an argument, the 
 output of a plotting command is displayed using the default ``matplotlib`` 
 backend in a separate window. Alternatively, the backend can be explicitly 
 requested using, for example::
 
   %matplotlib gtk
 
 A particularly interesting backend, provided by IPython, is the ``inline``
 backend.  This is available only for the IPython Notebook and the
 :ref:`IPython QtConsole <qtconsole>`.  It can be invoked as follows::
 
   %matplotlib inline
 
 With this backend, the output of plotting commands is displayed *inline*
 within the notebook, directly below the code cell that produced it. The
 resulting plots will then also be stored in the notebook document. 
 
 .. seealso::
 
     `Plotting with Matplotlib`_  example notebook
 
 
 Configuring the IPython Notebook
 --------------------------------
 The notebook server can be run with a variety of command line arguments. 
 To see a list of available options enter::
 
   $ ipython notebook --help 
 
 Defaults for these options can also be set by creating a file named 
 ``ipython_notebook_config.py`` in your IPython *profile folder*. The profile 
 folder is a subfolder of your IPython directory; to find out where it is 
 located, run::
 
   $ ipython locate
 
 To create a new set of default configuration files, with lots of information 
 on available options, use::
 
   $ ipython profile create
 
 .. seealso::
 
     :ref:`config_overview`, in particular :ref:`Profiles`.
     
     :ref:`notebook_server_security`
 
     :ref:`notebook_public_server`
 
 
 .. _signing_notebooks:
 
 Signing Notebooks
 -----------------
 
 To prevent untrusted code from executing on users' behalf when notebooks open,
 we have added a signature to the notebook, stored in metadata.
 The notebook server verifies this signature when a notebook is opened.
 If the signature stored in the notebook metadata does not match,
 javascript and HTML output will not be displayed on load,
 and must be regenerated by re-executing the cells.
 
 Any notebook that you have executed yourself *in its entirety* will be considered trusted,
 and its HTML and javascript output will be displayed on load.
 
 If you need to see HTML or Javascript output without re-executing,
 you can explicitly trust notebooks, such as those shared with you,
 or those that you have written yourself prior to IPython 2.0,
 at the command-line with::
 
     $ ipython trust mynotebook.ipynb [other notebooks.ipynb]
 
 This just generates a new signature stored in each notebook.
 
 You can generate a new notebook signing key with::
 
     $ ipython trust --reset
 
 
 Importing ``.py`` files
 -----------------------
 
 ``.py`` files will be imported as a notebook with 
 the same basename, but an ``.ipynb`` extension, located in the notebook 
 directory. The notebook created will have just one cell, which will contain 
 all the code in the ``.py`` file. You can later manually partition this into 
 individual cells using the ``Edit | Split Cell`` menu option, or the 
 :kbd:`Ctrl-m -` keyboard shortcut.
 
 Note that ``.py`` scripts obtained from a notebook document using :doc:`nbconvert <nbconvert>`
 maintain the structure of the notebook in comments. Reimporting such a
 script back into a notebook will preserve this structure.
 
 .. _note_about_roundtrip:
 
 .. warning::
 
    While in simple cases you can "roundtrip" a notebook to Python, edit the
    Python file, and then import it back without loss of main content, this is 
    in general *not guaranteed to work*.  First, there is extra metadata
    saved in the notebook that may not be saved to the ``.py`` format.  And as
    the notebook format evolves in complexity, there will be attributes of the
    notebook that will not survive a roundtrip through the Python form.  You
    should think of the Python format as a way to output a script version of a
    notebook and the import capabilities as a way to load existing code to get 
    a notebook started.  But the Python version is *not* an alternate notebook
    format.
 
 .. seealso::
-    :ref:`notebook_format`
+    :ref:`nbformat`
 
 .. include:: ../links.txt