@@ -74,9 +74,9 @@ axes via `.Axes.secondary_xaxis` and `.Axes.secondary_yaxis`. See
74
74
`~.scale.FuncScale ` for arbitrary axes scales
75
75
---------------------------------------------
76
76
77
- A new `- .scale.FuncScale ` class was added (and `- .scale.FuncTransform `)
77
+ A new `~ .scale.FuncScale ` class was added (and `~ .scale.FuncTransform `)
78
78
to allow the user to have arbitrary scale transformations without having to
79
- write a new subclass of `- .scale.ScaleBase `. This can be accessed by::
79
+ write a new subclass of `~ .scale.ScaleBase `. This can be accessed by::
80
80
81
81
ax.set_yscale('function', functions=(forward, inverse))
82
82
@@ -90,11 +90,11 @@ Legend for scatter
90
90
91
91
A new method for creating legends for scatter plots has been
92
92
introduced. Previously, in order to obtain a legend for a
93
- :meth: `- .axes.Axes.scatter ` plot, one could either plot several
93
+ :meth: `~ .axes.Axes.scatter ` plot, one could either plot several
94
94
scatters, each with an individual label, or create proxy artists to
95
95
show in the legend manually. Now,
96
- :class: `- .collections.PathCollection ` provides a method
97
- :meth: `- .collections.PathCollection.legend_elements ` to obtain the
96
+ :class: `~ .collections.PathCollection ` provides a method
97
+ :meth: `~ .collections.PathCollection.legend_elements ` to obtain the
98
98
handles and labels for a scatter plot in an automated way. This makes
99
99
creating a legend for a scatter plot as easy as
100
100
@@ -131,11 +131,11 @@ now directly forwards to the visibility of the underlying Rectangle artist
131
131
--------------------------------------
132
132
133
133
Matplotlib uses Pillow to handle saving to the JPEG and TIFF formats. The
134
- `- Figure.savefig() ` function gained a *pil_kwargs * keyword argument, which can
135
- be used to forward arguments to Pillow's `PIL .Image.save() `.
134
+ `~. Figure.savefig() ` function gained a *pil_kwargs * keyword argument, which can
135
+ be used to forward arguments to Pillow's `pillow .Image.save() `.
136
136
137
137
The *pil_kwargs * argument can also be used when saving to PNG. In that case,
138
- Matplotlib also uses Pillow's `PIL .Image.save() ` instead of going through its
138
+ Matplotlib also uses Pillow's `pillow .Image.save() ` instead of going through its
139
139
own builtin PNG support.
140
140
141
141
@@ -159,7 +159,7 @@ Axes and Artists
159
159
axes_grid1 and axisartist Axes no longer draw spines twice
160
160
----------------------------------------------------------
161
161
162
- Previously, spines of `axes_grid1 ` and `axisartist ` Axes would be drawn twice,
162
+ Previously, spines of `. axes_grid1 ` and `. axisartist ` Axes would be drawn twice,
163
163
leading to a "bold" appearance. This is no longer the case.
164
164
165
165
@@ -178,7 +178,7 @@ changed.
178
178
-----------------------------------------------
179
179
180
180
Alternatively to strings like ``"data" `` or ``"axes fraction" ``
181
- `ConnectionPatch ` now accepts any `- matplotlib.transforms.Transform `
181
+ `ConnectionPatch ` now accepts any `~ matplotlib.transforms.Transform `
182
182
as input for the ``coordsA `` and ``coordsB `` argument. This allows to
183
183
draw lines between points defined in different user defined coordinate
184
184
systems. Also see the :doc: `Connect Simple01 example
@@ -198,11 +198,11 @@ an existing Line3D.
198
198
``Axes3D.voxels `` now shades the resulting voxels
199
199
-------------------------------------------------
200
200
201
- The :meth: `- mpl_toolkits.mplot3d.Axes3D.voxels ` method now takes a
201
+ The :meth: `~ mpl_toolkits.mplot3d.Axes3D.voxels ` method now takes a
202
202
*shade * parameter that defaults to `True `. This shades faces based
203
203
on their orientation, behaving just like the matching parameters to
204
- :meth: `- mpl_toolkits.mplot3d.Axes3D.trisurf ` and
205
- :meth: `- mpl_toolkits.mplot3d.Axes3D.bar3d `. The plot below shows how
204
+ :meth: `~ mpl_toolkits.mplot3d.Axes3D.trisurf ` and
205
+ :meth: `~ mpl_toolkits.mplot3d.Axes3D.bar3d `. The plot below shows how
206
206
this affects the output.
207
207
208
208
.. plot ::
@@ -265,8 +265,8 @@ Default minor tick spacing was changed from 0.625 to 0.5 for major ticks spaced
265
265
A public API has been added to `EngFormatter ` to control how the
266
266
numbers in the ticklabels will be rendered. By default,
267
267
``useMathText `` evaluates to
268
- :rc: `rcParams[' axes.formatter.use_mathtext'] ` and ``usetex `` evaluates
269
- to :rc: `rcParams[ 'text.usetex'] `.
268
+ :rc: `axes.formatter.use_mathtext' ` and ``usetex `` evaluates
269
+ to :rc: `'text.usetex' `.
270
270
271
271
If either is `True ` then the numbers will be encapsulated by ``$ ``
272
272
signs. When using ``TeX `` this implies that the numbers will be shown
@@ -294,7 +294,7 @@ created with the Qt5 backend.
294
294
*progress_callback * argument to `~.Animation.save() `
295
295
----------------------------------------------------
296
296
297
- The method .FuncAnimation .save() gained an optional
297
+ The method ` .Animation .save` gained an optional
298
298
*progress_callback * argument to notify the saving progress.
299
299
300
300
@@ -337,7 +337,7 @@ were previously displayed as ``1e+04``.
337
337
MouseEvent button attribute is now an IntEnum
338
338
---------------------------------------------
339
339
340
- The :attr: `button ` attribute of `- .MouseEvent ` instances can take the values
340
+ The :attr: `button ` attribute of `~ .MouseEvent ` instances can take the values
341
341
None, 1 (left button), 2 (middle button), 3 (right button), "up" (scroll), and
342
342
"down" (scroll). For better legibility, the 1, 2, and 3 values are now
343
343
represented using the `IntEnum ` class `matplotlib.backend_bases.MouseButton `,
0 commit comments