I guess there isn't a way to ignore this for only stubtest and not mypy (which I assume wouldn't import since it's static)?

Yeah, stubtest has config to filter out identified warnings, but not to avoid.

Technically possible to have a separate config file, but having parallel mostly the same configs seems like a poor choice. Especially when mypy the thing being ignored has no type hints, so mypy is rather pointless on that file (and even if we add type hints to tinypages at some point, it is so short, disconnected from other code, and rarely changed that a manual check is not so bad)

it is so short, disconnected from other code, and rarely changed that a manual check is not so bad

But #25515! Though I don't think that type checking is at all relevant in here ;-)

I mean yeah (I know you were mostly joking, but that PR actually reinforces my point if anything). The only changed file from #25515 affected by the ignore introduced here is the conf.py (which still doesn't have type hints, so mypy checking it is rather unnecessary). The rst file changes would always be ignored by mypy/stubtest/etc.

I could have done a bit more targeted of an ignore (only the tinypages example with plt.show() was actually problematic, specifically because stubtest imports everything), but the whole folder is untyped, so may as well, and cross the bridge of enabling checks if/when it becomes typed. Being a bit more broad means the changes to tinypages (like #25515) can happen more freely until then.