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

[Mike C]

I can only compare to the R language I've used. If there is an issue, say a function freezes at startup, one user brings it up to the list, when the respective maintainer sees the bug, it is usually addressed on the next release.

In terms of funding. Isn't Python heavily used in industry, so, financial contribution should've been huge, no?


________________________________
From: Tutor <tutor-bounces+tmrsg11=gmail.com at python.org> on behalf of Steven D'Aprano <steve at pearwood.info>
Sent: Friday, June 15, 2018 8:33:54 PM
To: tutor at python.org
Subject: Re: [Tutor] In matplotlib, why are there axes classes vs. axes API? Why not list them under one documentation?

On Fri, Jun 15, 2018 at 12:35:36PM -0400, C W wrote:

> Why haven't the developers fixed the problem?

matplotlib is free, open source software. If volunteers don't "fix the
problem", who is paying for the work to be done?

Are you volunteering?

Or willing to pay somebody to do the work? $30,000 - $50,000 would
probably pay for one developer to work on mathplotlib full time for
three months.

Or maybe the developers don't think it is a problem that needs fixing.
Maybe they're happy with it the way it is.

Or they don't like it any more than you do, but they are constrained by
the need to keep backwards compatibility.


--
Steve
_______________________________________________
Tutor maillist  -  Tutor at python.org
To unsubscribe or change subscription options:
https://mail.python.org/mailman/listinfo/tutor