Conversation
If I recall, the main reason it is an Axes rather than an Axis, is that Axis does not have the concept of an x/ylabel - that is an Axes property. Similarly I think there are numerous tick conveniences on Axes that are less easy on Axis. Not to say one couldn't come up with an API for multiple xlabels etc, but simplest was just a child Axes. |
|
While pragmatism tells me to merge this, this feels wrong. While we interpret type fields loosely target towards readability (instead of formal type specifications), the type field is not the place for context information. The minimal solution would be to move that to the description. OTOH, the underlying problem is that |
|
Fair enough. I don't really have bandwidth to propose a better change right now, so let's just close this. |

PR summary
I had expected
secondary_xaxisto return something that behaves likeXAxis, so was surprised to getPR checklist