This allows specifying the output base name of the generated image files. The
name can include '{counter}', which is automatically string formatted to an
incrementing counter. The default if it is not specified is left intact as
the current behavior, which is to use the base name of the provided script or
the RST document.

This is required to use the plot directive with MyST, because the directive is
broken with MyST (an issue I don't want to fix), requiring the use of
eval-rst. But the way eval-rst works, the incrementing counter is not
maintained across different eval-rst directives, meaning if you try to include
multiple of them in the same document, the images will overwrite each other.
This allows you to manually work around this with something like

```{eval-rst}
.. plot::
   :output-base-name: plot-1

   ...
```

```{eval-rst}
.. plot::
   :output-base-name: plot-2

   ...
```

Aside from this, it's generally useful to be able to specify the image name
used for a plot, as a more informative name can be used rather than just
'<document-name>-1.png'.

The idea of allowing the use of the counter for custom base names is flawed
because the counter would always be incremented even for custom names that
don't use it. Also, the global base name is difficult to get working because
we don't have a good global view of the plots to create a counter, especially
in the case of partial rebuilds.

Instead, we just simplify things by just allowing setting a custom-base-name.
If two plot directives use the same custom-base-name, then one will end up
overwriting the other (I'm still looking into whether it's possible to at
least detect this and give an error).

Previously it would just overwrite one plot with the other.

I did not add tests for this because I would have to create a whole separate
docs build just to test the error (but I have tested it manually).

This will hopefully fix Sphinx trying and failing to include it.

Co-authored-by: Elliott Sales de Andrade <[email protected]>

…xtension

…docs in tinypages

The tests now don't copy any of the build files, meaning the tests should pass
even if tinypages has stale build state from a manual build.

We now subset Type-1 fonts and no longer have a copy of ttconv.

Make the font comparison table a grid table so we can use a colspan
cell.

Clarify that Type-1 fonts get used only in the usetex/pdf combination.

Signed-off-by: ianlv <[email protected]>

chore: remove redundant words in comment

…ce-rc

* WIP: changed FancyArrow empty logic

* Update test_patches.py

* Update test_patches.py

* Fix crash when drawing FancyArrow with zero length

* Update patches.py

* Delete .python-version

Upgrade to Visual Studio 2022 in appveyor.yml

They remain in `style.library`, because that's how we look them up, but
this prevents them being exposed as something someone might use.

Also, fix `reload_library`, which was accidentally modifying the
original base library information each time.

Fixes itprojects/MasVisGtk#13

Add explicit `**options: Any` for `add_subplot` method

Time out after 30 seconds. This is used for version queries which
should be very fast, so a 30-second delay would be unusual.

GitHub Actions test runs have been hanging trying to get the
inkscape version when using Python 3.14:

https://github.com/matplotlib/matplotlib/actions/runs/16043158943/job/45268507848#step:13:836

…ble-info

Time out in _get_executable_info

ruff uses `project.requires-python`, so the ruff-only `target-version`
is not needed.

Other exceptions can be dropped since they are all clear of warnings.

The removed excludes are covered by the first line. The Unpack feature
was enabled by default in 1.9, which is our minimum.

These examples only needed a single fix to remove the exception.

This also has the side-effect of casting torch Tensors to NumPy arrays,
which fixes matplotlib#30216. Since `stem` is made up of `plot` and `[hv]lines`
whic already do this cast, this just moves it up one level which
prevents doing it twice.

Make the difference between the two methods clearer (only the latter
takes clipping into account).

Tweak docstrings of get_window_extent/get_tightbbox.

Clean up mypy & ruff config

Check that stem input is 1D

Fix figure legend when drawing stackplots

Don't expose private styles in style.available

This was originally for i686 on Fedora, but is now applicable to WASM,
which is 32-bit. The older implementation doesn't OOM.

Use old stride_windows implementation on 32-bit builds