[Matplotlib-devel] What minimum version of python3?

[Thomas Caswell]

Put this into the docs via
https://github.com/matplotlib/matplotlib/pull/10824

Tom

On Sat, Mar 3, 2018 at 1:50 PM Matthew Brett <matthew.brett at gmail.com>
wrote:

> Hi,
>
> On Sat, Mar 3, 2018 at 6:40 PM, Thomas Caswell <tcaswell at gmail.com> wrote:
> > We discussed the minimum python again on the call this past week and
> settled
> > on:
> >
> >  - support minor versions of python initially released in the previous 3
> > years
> >  - support minor versions of python initially released in the previous 3
> > years or oldest that supports the minimum python version (which ever is
> > higher)
> >
> > We will bump the minimum python an numpy versions as we can every minor
> and
> > major release.
> >
> > We did not discuss other dependencies, but I propose:
> >  - for system/c-dependencies (libpng, freetype, GUI frameworks, latex,
> gs,
> > ffmpeg) support as old as practical
> >  - for python dependencies with compiled extensions 3 years or the oldest
> > that support our minimum python + numpy
> >  - for python dependencies without complied extensions at least 2 years
> or
> > the oldest that supports our minimum python.
> >
> > Bump these minimum versions as they no longer support our minimum python
> or
> > we want to use new features in them.
> >
> > We should never bump minimum versions on a patch release.
> >
> > For mpl 3.0 (July 2018) this means python 3.5 (released Sept 2015) and
> numpy
> > 1.10 (release in Oct 2015).  Python 3.4 was released Mar 2014 and  Numpy
> 1.9
> > was released Sept 2014
> >
> > For mpl 3.1 (January 2019) this means python 3.6 (released Dec 2016) and
> > numpy 1.11 (March 2016).
>
> That seems very reasonable to me ...
>
> Cheers,
>
> Matthew
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/matplotlib-devel/attachments/20180317/0d994051/attachment.html>