@greglucas just noticing that I'm hitting the issue fixed by this on a fresh Python 3.14.0t environment. And indeed, the latest release is 3.10.7, so this fix isn't included. Does it maybe make sense to backport?

This does not feel like a back-port type thing to me, but could be talked into it.

I would generally agree that this seems potentially odd to put in a bugfix release. On the other hand, this is pretty niche still and I'm not sure guarantees us to anything as it is pretty heavily opt-in at this point still.

It has been 10 months since our last release https://github.com/matplotlib/matplotlib/releases/tag/v3.10.0, so I think people in the community are getting excited about updates and new features and wondering when they will be released, so I do understand the desire to get the features people have added out in some kind of release. I'm not sure if another bugfix release will happen again before the next version's release though, so maybe a backport is moot here 🤷

Actually, I do think this is valid for a backport because it was a bug that we forgot to mark this specific module in the original PR adding this declaration, so in a sense this is fixing that oversight.
#28819

@meeseeksdev backport to v3.10.x