You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As argued elsewhere, a customization point which requires third-party
libraries to override a private method is awkward from the PoV of
documentation and of required API stability. In fact _init_toolbar is
not needed as a customization point; third-party libraries can simply
override `__init__` and call `super().__init__` as appropriate.
Moreover, *requiring* that `_init_toolbar` be overridden is actually
overkill, e.g. for `test_backend_bases.py::test_interactive_zoom`:
there, the base class NavigationToolbar2 is perfectly suitable -- see
change there.
In order to let third-parties write code that supports both pre- and
post-deprecation versions of mpl, allow them to keep a fully empty
`_init_toolbar` (an override is required by earlier versions of mpl)
without triggering a deprecation warning.
0 commit comments