##// END OF EJS Templates
Backport PR #8829: Qt5 fix...
Backport PR #8829: Qt5 fix Fix for issue #8757. The problem was that IPython.external.qt was moved to qtconsole.qt, but IPython.external.qt_for_kernel was still trying to import IPython.external.qt. Rather than copying the qt.py file back to external, this PR merges the logic back into qt_for_kernel.py. Deferring to qt.py was a bit silly because both qt.py and qt_for_kernel.py do basically the same thing but in slightly different ways. Moreover, the assumption of qt.py was that if the QT_API environment variable is set, it must be in an ETS environment and need to comply by the ETS import logic. This is not valid, as ipython sets the QT_API environment variable to communicate intent as to Qt version, in `IPython/lib/inputhook.py:385` ...

File last commit:

r21587:4a6a7390
r21823:e0eb38c1
Show More
plotting.rst
36 lines | 1.4 KiB | text/x-rst | RstLexer
Jonathan Frederic
Add files remove in https://github.com/jupyter/notebook/pull/124
r21584 .. _plotting:
Plotting
--------
Jonathan Frederic
@takluyver's suggested changes...
r21587 One major feature of the IPython kernel is the ability to display plots that
Jonathan Frederic
Add files remove in https://github.com/jupyter/notebook/pull/124
r21584 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 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
Jonathan Frederic
@takluyver's suggested changes...
r21587 :ref:`Jupyter QtConsole <qtconsole>`. It can be invoked as follows::
Jonathan Frederic
Add files remove in https://github.com/jupyter/notebook/pull/124
r21584
%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
Jonathan Frederic
@takluyver's suggested changes...
r21587
.. include:: ../links.txt