Skip to content

Commit c1df30e

Browse files
tacaswelloscargus
andcommitted
DOC: fix line wrapping
Co-authored-by: Oscar Gustafsson <[email protected]>
1 parent 19c9011 commit c1df30e

File tree

2 files changed

+7
-6
lines changed

2 files changed

+7
-6
lines changed

examples/subplots_axes_and_figures/multiple_figs_demo.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,8 @@
1010
1111
.. note::
1212
13-
We discourage working with multiple figures through the implicit pyplot interface
14-
because managing the *current figure* is cumbersome and
13+
We discourage working with multiple figures through the implicit pyplot
14+
interface because managing the *current figure* is cumbersome and
1515
error-prone. Instead, we recommend using the explicit approach and call
1616
methods on Figure and Axes instances. See :ref:`api_interfaces` for an
1717
explanation of the trade-offs between the implicit and explicit interfaces.

lib/matplotlib/__init__.py

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -19,10 +19,11 @@
1919
2020
For the most part, direct use of the explicit object-oriented library is
2121
encouraged when programming; the implicit pyplot interface is primarily for
22-
working interactively. The exceptions to this suggestion are the pyplot functions
23-
`.pyplot.figure`, `.pyplot.subplot`, `.pyplot.subplots`, and `.pyplot.savefig`,
24-
which can greatly simplify scripting. See :ref:`api_interfaces` for an
25-
explanation of the tradeoffs between the implicit and explicit interfaces.
22+
working interactively. The exceptions to this suggestion are the pyplot
23+
functions `.pyplot.figure`, `.pyplot.subplot`, `.pyplot.subplots`, and
24+
`.pyplot.savefig`, which can greatly simplify scripting. See
25+
:ref:`api_interfaces` for an explanation of the tradeoffs between the implicit
26+
and explicit interfaces.
2627
2728
Modules include:
2829

0 commit comments

Comments
 (0)