##// END OF EJS Templates
Merge pull request #10203 from ipython/auto-backport-of-pr-10198...
Merge pull request #10203 from ipython/auto-backport-of-pr-10198 Backport PR #10198 on branch 5.x

File last commit:

r22598:f4fdafb6
r23240:8f5b6934 merge
Show More
plotting.rst
42 lines | 1.6 KiB | text/x-rst | RstLexer

Plotting

One major feature of the IPython kernel is the ability to display plots that are the output of running code cells. The IPython kernel is designed to work seamlessly with the matplotlib_ plotting library to provide this functionality.

To set this up, before any plotting or import of matplotlib 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 Jupyter Notebook and the Jupyter QtConsole. It can be invoked as follows:

%matplotlib inline

With this backend, the output of plotting commands is displayed inline within frontends like the Jupyter notebook, directly below the code cell that produced it. The resulting plots will then also be stored in the notebook document.

The matplotlib_ library also ships with %matplotlib notebook command that allows interactive figures if your environment allows it.

See the matplotlib_ documentation for more information.