Third release candidate for Python 3.4

The third release candidate for Python 3.4 has been released.

You can also retrieve the source code using Mercurial from the http://hg.python.org/releasing/3.4/.

What's New in Python 3.4 has been updated with the latest changes and is closed to its final draft form.

First release candidate of Python 3.4 released

The first release candidate for Python 3.4, Python 3.4.0rc1, has been issued on February 10 2014. This is a preview release of the next major release of Python, Python 3.4, and is not yet suitable for production environments.
The new features added to Python 3.4 are described in more detail in What's New in Python 3.4.

Python 3.3.4 is now available

A new maintenance release, Python 3.3.4, was released on February 9 2014.

This release fully supports OS X 10.9 Mavericks. In particular, this release fixes an issue that could cause previous versions of Python to crash when typing in interactive mode on OS X 10.9.

Python 3.3.3 relased

A new maintenance release, Python 3.3.3, has been released on November 13 2013.

Python 2.7.6 released

A new maintenance release, Python 2.7.6, has been released on November 10 2013. This is a 2.7 series bugfix release resolving an issue that caused the interactive prompt to crash on OS X 10.9. It also includes numerous bugfixes over 2.7.5.

Python 2.6.9 is now available

The final release of Python 2.6.9 is now available, released on October 29 2013. This is a source-only release for Python 2.6.8, fixing several reported security issues, and will be the final release of the 2.6 series.

Introducing Electronic Contributor Agreements

We're happy to announce the new way to file a contributor agreement: on the web at http://www.python.org/psf/contrib/contrib-form/.

Through the use of Adobe's EchoSign, we got rid of the old hand-written, print out, scan or photograph, then fax or email of your form. It was a hassle for our contributors, and a hassle for our administrators. Faxes fail, mail gets lost, and sometimes pictures or scans turn out poorly. It was time to find a more user-friendly solution, and the Foundation is happy to finally offer this electronic form.


The new form is easy to fill out right on the site, guiding you through each of the required fields such as your name, bug tracker ID, address, and initial license. If you're signing the form on behalf of an organization, there's a check box to specify this, and then you are asked near the bottom to state your title in the organization. Lastly, your signature is either generated from your typed name, or you can draw your own or upload a signature file of your own.

Once you submit the form, you'll receive an email from echosign.com to verify the email address you entered. Once you click to confirm your address, the form will be emailed to the PSF and will be recorded.


We require all contributors to CPython to have a signed form, and we hope this makes it easier for potential contributors to join up and help make Python better. It's available just in time for PyCon and the CPython sprint that will be occurring March 18 through 21 in Santa Clara, California. Join us at the sprint, sign your contributor form, and help us fix some bugs or add some features!