simultaneously with the new name), but suppport for it will be dropped in

Setting the same artist property multiple time via aliases is deprecated

Previously, code such as ``plt.plot([0, 1], c="red", color="blue")`` would

emit a warning indicating that ``c`` and ``color`` are aliases of one another,

and only keep the ``color`` kwarg. This behavior has been deprecated; in a

future version, this will raise a TypeError, similar to Python's behavior when

a keyword argument is passed twice (``plt.plot([0, 1], c="red", c="blue")``).

This warning is raised by `~.cbook.normalize_kwargs`.

Boxplot tick methods

The ``manage_xticks`` parameter of `~Axes.boxplot` and `~Axes.bxp` has been

renamed (with a deprecation period) to ``manage_ticks``, to take into account

the fact that it manages either x or y ticks depending on the ``vert``

parameter.

When ``manage_ticks`` is True (the default), these methods now attempt to take

previously drawn boxplots into account when setting the axis limits, ticks, and

tick labels.

`matplotlib.use` parameter change

The first parameter of `matplotlib.use` has been renamed from *arg* to

*backend*. This will only affect cases where that parameter has been set

as a keyword argument. The common usage pattern as a positional argument

``matplotlib.use('Qt5Agg')`` is not affected.

Exception on failing animations changed

Previously, subprocess failures in the animation framework would raise either

in a `RuntimeError` or a `ValueError` depending on when the error occurred.

They now raise a `subprocess.CalledProcessError` with attributes set as

documented by the exception class.

MouseEvents now include the event name in their ``str()``

Previously they contained the prefix "MPL MouseEvent".

Matplotlib.use now has an ImportError for interactive backend

Switching backends via `matplotlib.use` is now allowed by default,

regardless of whether `matplotlib.pyplot` has been imported. If the user

tries to switch from an already-started interactive backend to a different

interactive backend, an ImportError will be raised.

Path code types like ``Path.MOVETO`` are now ``np.uint8`` instead of ``int``

``Path.STOP``, ``Path.MOVETO``, ``Path.LINETO``, ``Path.CURVE3``,

``Path.CURVE4`` and ``Path.CLOSEPOLY`` are now of the type ``Path.code_type``

(``np.uint8`` by default) instead of plain ``int``. This makes their type

match the array value type of the ``Path.codes`` array.

Allow "real" LaTeX code for ``pgf.preamble`` and ``text.latex.preamble`` in matplotlib rc file

Previously, the rc file keys ``pgf.preamble`` and ``text.latex.preamble`` were parsed using commmas as separators. This would break valid LaTeX code, such as::

\usepackage[protrusion=true, expansion=false]{microtype}

The parsing has been modified to pass the complete line to the LaTeX system,

keeping all commas.

Passing a list of strings from within a Python script still works as it used to.

Passing a list containing non-strings now fails, instead of coercing the results to strings.

matplotlib.font_manager.win32InstalledFonts return value

`matplotlib.font_manager.win32InstalledFonts` returns an empty list instead

of None if no fonts are found.

``Cn`` colors now support ``n>=10``

It is now possible to go beyond the tenth color in the property cycle using

``Cn`` syntax, e.g. ``plt.plot([1, 2], color="C11")`` now uses the 12th color

in the cycle.

Note that previously, a construct such as ``plt.plot([1, 2], "C11")`` would be

interpreted as a request to use color ``C1`` and marker ``1`` (an "inverted Y").

To obtain such a plot, one should now use ``plt.plot([1, 2], "1C1")`` (so that

the first "1" gets correctly interpreted as a marker specification), or, more

explicitly, ``plt.plot([1, 2], marker="1", color="C1")``.

Changes to the internal tick handling API

``Axis.iter_ticks`` (which only served as a helper to the private

``Axis._update_ticks``) is deprecated.

The signature of the (private) ``Axis._update_ticks`` has been changed to not

take the renderer as argument anymore (that argument is unused).

Deprecations

Support for custom backends that do not provide a ``set_hatch_color`` method is

deprecated. We suggest that custom backends let their ``GraphicsContext``

class inherit from `GraphicsContextBase`, to at least provide stubs for all

required methods.

The fields ``Artist.aname`` and ``Axes.aname`` are deprecated. Please use

``isinstance()`` or ``__class__.__name__`` checks instead.``Axes.fmt_xdata`` and ``Axes.fmt_ydata`` no longer ignore TypeErrors raised by a user-provided formatter

Previously, if the user provided a ``fmt_xdata`` or ``fmt_ydata`` function that

raised a TypeError (or set them to a non-callable), the exception would be

silently ignored and the default formatter be used instead. This is no longer

the case; the exception is now propagated out.

Axes methods now raise TypeError instead of RuntimeError on mismatched calls

In certain cases, Axes methods (and pyplot functions) used to raise a

RuntimeError if they were called with a ``data`` kwarg and otherwise mismatched

arguments. They now raise a ``TypeError`` instead.

Changes to `matplotlib.axes.Axes.spy`

The method `matplotlib.axes.Axes.spy` now raises a TypeError for the keyword

arguments 'interpolation' and 'linestyle' instead of silently ignoring them.

Furthermore, `matplotlib.axes.Axes.spy` spy does now allow for an 'extent'

argument (was silently ignored so far).

A bug with `spy(..., origin='lower') is fixed: So far this flipped the

actual data indices. Now, `origin='lower'` flips both the data and the y-axis

`FigureCanvasAgg.buffer_rgba` and `RendererAgg.buffer_rgba` now return a memoryview

The ``buffer_rgba`` method now allows direct access to the renderer's

underlying buffer (as a ``(m, n, 4)``-shape memoryview) rather than copying the

data to a new bytestring. This is consistent with the behavior on Py2, where a

buffer object was returned.