[Matplotlib-devel] long term schedule

[Thomas Caswell]

I should have said "no more api breakage than normal between point
releases".

We do not want to get in to a situation where major down stream packages
that is mpl (yt, skimage, pandas, etc) pin a maximum matplotlib version.

Tom

On Fri, May 20, 2016, 14:32 Eric Firing <efiring at hawaii.edu> wrote:

> On 2016/05/20 8:18 AM, OceanWolf via Matplotlib-devel wrote:
> > How does "not breaking any APIs" influence the deprecation and removal
> > timeline for the gui overhaul?  I thought perhaps deprecate in 2.2 and
> > remove in 3.0?  Or does such a timeline go too fast?
> >
> Along the same lines, I think this might be too much of a straitjacket.
> This is a vague sense of unease--I don't have a specific example.  It
> just seems like having to keep *everything* 100% intact until a 4.0
> release in 2019 or 2020 might be going too far.  This is especially so
> since "API" is not so well defined.  Does every attribute lacking a
> leading underscore have to be maintained for several more years?  Maybe
> "API" needs a qualifier, like "major API".
>
> Eric
>
> _______________________________________________
> Matplotlib-devel mailing list
> Matplotlib-devel at python.org
> https://mail.python.org/mailman/listinfo/matplotlib-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20160520/b58c04cd/attachment-0001.html>