Release Schedules

OpenPGP Public Keys

Source and binary executables are signed by the release manager or binary builder using their OpenPGP key. Release files for currently supported releases are signed by the following:

Release files for older releases which have now reached end-of-life may have been signed by one of the following:

You can import a person's public keys from a public keyserver network server you trust by running a command like:

gpg --recv-keys [key id]

or, in many cases, public keys can also be found at keybase.io. On the version-specific download pages, you should see a link to both the downloadable file and a detached signature file. To verify the authenticity of the download, grab both files and then run this command:

gpg --verify Python-3.6.2.tgz.asc

Note that you must use the name of the signature file, and you should use the one that's appropriate to the download you're verifying.

  • (These instructions are geared to GnuPG and Unix command-line users.)

Other Useful Items

  • Looking for 3rd party Python modules? The Package Index has many of them.
  • You can view the standard documentation online, or you can download it in HTML, PostScript, PDF and other formats. See the main Documentation page.
  • Information on tools for unpacking archive files provided on python.org is available.
  • Tip: even if you download a ready-made binary for your platform, it makes sense to also download the source. This lets you browse the standard library (the subdirectory Lib) and the standard collections of demos (Demo) and tools (Tools) that come with it. There's a lot you can learn from the source!
  • There is also a collection of Emacs packages that the Emacsing Pythoneer might find useful. This includes major modes for editing Python, C, C++, Java, etc., Python debugger interfaces and more. Most packages are compatible with Emacs and XEmacs.

Want to contribute?

Want to contribute? See the Python Developer's Guide to learn about how Python development is managed.