Since that's the only thing in there, should we change the import in the.py file, too?

I mean, logically yes, but technically at runtime more gets imported there, just not things weintend to re-export.

I was being a bit conservative here andonly changing stub behavior (especially since the stubsdidn't pick upSubplot as being exported, when itshould be)

I actually think__init__.py files (broadly) are good candidates for inlining type hints and just not having separate files: they are short, contain little to no actual function definitions, it's mostly imports and__all__ (which I'm also in favor of adding in more places)

Looking at__clear, I see alsolegend_ andtitle that aren't here; should they be added as well? (The former appears inaxes.pyi onAxes)

I'd say those ones (and perhaps several of the existing attrs) should be made private (title there is already_[left|right]_title whichare private, though the getters/setters are defined in_axes.py, not_base.py, for some reason, and not defined forsecondary_axes, even though the attrs exist)

But I'll add them since they are by naming convention public (though I will also note that none of these attrs (aside fromdataLim andviewLim) actually appear in the rendered docs, though several (trans[Axes,Scale,Limits,Data] come to mind)are referred to by examples, etc. Is that something wewant to include in the rendered docs? cc@timhoffm, this is reminiscent of the discussions regardingplt.Axes/plt.Figure, but is different in that these are not imports and are instance attributes)

ax.title is used in several tests as well as thelifecycle tutorial andtight_layout_guide

axes.legend_ is used outside of theaxes module only inbackend/qt_editor/figureoptions.py as far as I can tell through quick greps (and never in documentation)