[Tutor] In matplotlib, why are there axes classes vs. axes API? Why not list them under one documentation?

[C W]

I read through some documentations yesterday after posting.

I will share what I think. There are three parts to matplotlib: backend,
artist, and scripting. The artist layer is the only one that really matters
for matplotlib users.

Why haven't the developers fixed the problem? Considering Python's growing
popularity, hasn't anyone brought this up before me? Was there a plan?

Thanks!





On Thu, Jun 14, 2018 at 9:39 PM, Steven D'Aprano <steve at pearwood.info>
wrote:

> On Thu, Jun 14, 2018 at 12:31:44PM -0400, C W wrote:
> > Hello everyone,
> >
> > I'm working on matplotlib, could someone explain the difference between
> > these two?
> >
> > Axes class: https://matplotlib.org/api/axes_api.html#matplotlib.axes.
> Axes
> > Axes and tick API: https://matplotlib.org/api/axis_api.html
> >
> > I began at reading axes class, but discovered axes API by accident. Why
> are
> > there two documentations on the same thing? Why not merge? I mean, one is
> > already confusing enough. ;)
>
> *shrug*
>
> Because the designers of matplotlib suck at designing a good, easy to
> use, easy to understand, simple API? Because they're not good at writing
> documentation? I dunno.
>
> It is hard to write an API which is both *obvious* and *powerful*, but
> the few times I tried using matplotlib I found it baroque and confusing.
>
>
>
> --
> Steve
> _______________________________________________
> Tutor maillist  -  Tutor at python.org
> To unsubscribe or change subscription options:
> https://mail.python.org/mailman/listinfo/tutor
>