You are reading an old version of the documentation (v1.5.0). For the latest version see

We're updating the default styles for Matplotlib 2.0

Learn what to expect in the new updates


Table Of Contents

Previous topic

Documenting matplotlib

Next topic

Working with transformations

This Page

Doing a matplotlib release

A guide for developers who are doing a matplotlib release.

  • Edit and bump the version number


  • Run all of the regression tests by running python test script at the root of the source tree.
  • Run unit/ and make sure there are no memory leaks
  • try some GUI examples, e.g., with GTKAgg, TkAgg, etc...
  • remove font cache and tex cache from .matplotlib and test with and without cache on some example script
  • Optionally, make sure examples/tests/ runs without errors and check the output of the PNG, PDF, PS and SVG backends


Once all the tests are passing and you are ready to do a release, you need to create a release branch. These only need to be created when the second part of the version number changes:

git checkout -b v1.1.x
git push [email protected]:matplotlib/matplotlib.git v1.1.x

On the branch, do any additional testing you want to do, and then build binaries and source distributions for testing as release candidates.

For each release candidate as well as for the final release version, please git tag the commit you will use for packaging like so:

git tag -a v1.1.0rc1

The -a flag will allow you to write a message about the tag, and affiliate your name with it. A reasonable tag message would be something like v1.1.0 Release Candidate 1 (September 24, 2011). To tag a release after the fact, just track down the commit hash, and:

git tag -a v1.0.1rc1 a9f3f3a50745

Tags allow developers to quickly checkout different releases by name, and also provides source download via zip and tarball on github.

Then push the tags to the main repository:

git push upstream v1.0.1rc1


  • Make sure the is up to date and remove MANIFEST so it will be rebuilt by
  • run git clean in the mpl git directory before building the sdist
  • unpack the sdist and make sure you can build from that directory
  • Use setup.cfg to set the default backends. For windows and OSX, the default backend should be TkAgg. You should also turn on or off any platform specific build options you need. Importantly, you also need to make sure that you delete the build dir after any changes to setup.cfg before rebuilding since cruft in the build dir can get carried along.
  • On windows, unix2dos the rc file.
  • We have a Makefile for the OS X builds in the mpl source dir release/osx, so use this to prepare the OS X releases.
  • We have a Makefile for the win32 mingw builds in the mpl source dir release/win32 which you can use this to prepare the windows releases.

Update PyPI

This step tells PyPI about the release and uploads a source tarball. This should only be done with final (non-release-candidate) releases, since doing so will hide any available stable releases.

You may need to set up your pypirc file as described in the distutils register command documentation.

Then updating the record on PyPI is as simple as:

python register

This will hide any previous releases automatically.

Then, to upload the source tarball:

rm -rf dist
python sdist upload

Documentation updates

The built documentation exists in the repository. Pushing changes to master automatically updates the website.

The documentation is organized by version. At the root of the tree is always the documentation for the latest stable release. Under that, there are directories containing the documentation for older versions as well as the bleeding edge release version called dev (usually based on what’s on master in the github repository, but it may also temporarily be a staging area for proposed changes). There is also a symlink directory with the name of the most recently released version that points to the root. With each new release, these directories may need to be reorganized accordingly. Any time these version directories are added or removed, the versions.html file (which contains a list of the available documentation versions for the user) must also be updated.

To make sure everyone’s hard work gets credited, regenerate the github stats. cd into the tools directory and run:

python $TAG > ../doc/users/github_stats.rst

where $TAG is the tag of the last major release. This will generate stats for all work done since that release.

In the matplotlib source repository, build the documentation:

cd doc
python html
python latex

Then copy the build products into your local checkout of the repository (assuming here to be checked out in com:

cp -r build/html/* ~/
cp build/latex/Matplotlib.pdf ~/

Then, from the directory, commit and push the changes upstream:

git commit -m "Updating for v1.0.1"
git push upstream master


Announce the release on matplotlib-announce, matplotlib-users, and matplotlib-devel. Final (non-release-candidate) versions should also be announced on python-announce. Include a summary of highlights from the CHANGELOG and/or post the whole CHANGELOG since the last release.