Does not render for some reason.

it's rendered here, but getting lost:
https://output.circle-artifacts.com/output/job/33765224-5d37-442d-9e80-dfb6348738b2/artifacts/0/doc/build/html/api/testing_api.html#data-container-testing-fixtures

Was wondering if I should maybe add sample usage to the docstrings

That's what I meant. For some reason autofunction does not produce content here.

If nothing else helps, you could resort to a manual .. Py::function::. Not preferred to have doc content in rst away from the function, IMHO bearable in this special case.

Weird cause it works locally:

Theory: I suspect the reason is that matplotlib.testing.conftest imports pytest. This fails because pytest is not present in the doc build environment. I know that Sphinx autodoc silently ignores failed package imports and does not produce output in this case.

You may try autodoc_mock_imports but I don't know whether that can mock decorators (if not you will still fail when the import ties to run the @pytest.fixture).

@story645 you can add the usage examples or merge immediately - as you see fit.

I'm locally building the usage examples, will push in a bit

I so don't understand how it's even more broken now

how would you all feel about more pre-commits: https://numpydoc.readthedocs.io/en/latest/validation.html

Well, it currently outputs a 27K-line table of issues on just the files in lib/matplotlib/*.py, so I'm not sure how feasible that is right now.

Well, it currently outputs a 27K-line table of issues on just the files in lib/matplotlib/*.py, so I'm not sure how feasible that is right now.

I know linting fix PRs aren't folks faves, but this seems like a good low hanging fruit task for sprints

I know linting fix PRs aren't folks faves, but this seems like a good low hanging fruit task for sprints

Fine as long as the resulting PRs are trivial to review (small enough, only one kind of change at a time).

I suspect the 27k-lines of issues contain a lot of aspects that we cannot or don't want to fulfill. I think you'd have to start with a checks whitelist to work your way up and not get overwhelmed with messages. Then, when the big chunks are done, switch to the blacklist and narrow down further.