Version 3.0.2
matplotlib
Fork me on GitHub

Table of Contents

Minimum Version of Dependencies Policy

For the purpose of this document, 'minor version' is in the sense of SemVer (major, minor, patch) and includes both major and minor releases. For projects that use date-based versioning, every release is a 'minor version'.

Python and numpy

  • support minor versions of Python initially released 36 months prior to our planned release date.
  • support minor versions of numpy initially released in the 36 months prior to our planned release date or oldest that supports the minimum python version (which ever is higher)

We will bump the minimum python and numpy versions as we can every minor and major release, but never on a patch release.

Python Dependencies

For python dependencies we should support at least:

with compiled extensions
minor versions initially released in the 36 months prior to our planned release date or the oldest that support our minimum python + numpy
without complied extensions
minor versions initially released in the 24 months prior to our planed release date or the oldest that supports our minimum python.

We will only bump these dependencies as we need new features or the old versions no longer support our minimum numpy or python.

Test and Documentation Dependencies

As these packages are only needed for testing or building the docs and not needed by end-users, we can be more aggressive about dropping support for old versions. However, we need to be careful to not over-run what down-stream packagers support (as most of the run the tests and build the documentation as part of the packaging process).

We will support at least minor versions of the development dependencies released in the 12 months prior to our planned release.

We will only bump these as needed or versions no longer support our minimum Python and numpy.

System and C-dependencies

For system or c-dependencies (libpng, freetype, GUI frameworks, latex, gs, ffmpeg) support as old as practical. These can be difficult to install for end-users and we want to be usable on as many systems as possible. We will bump these on a case-by-case basis.