The Python programming language
Clone or download
serhiy-storchaka bpo-34974: Do not replace unexpected errors in bytes() and bytearray(…
…). (GH-9852)

bytes and bytearray constructors converted unexpected exceptions
(e.g. MemoryError and KeyboardInterrupt) to TypeError.
Latest commit e890421 Oct 14, 2018
Failed to load latest commit information.
.azure-pipelines bpo-34902: Fixes VM image for Azure Pipelines build (GH-9719) Oct 5, 2018
.github Add myself for HTML-related modules (#9325) Sep 15, 2018
Doc Update compound_stmts.rst (#9864) Oct 14, 2018
Grammar bpo-32117: Allow tuple unpacking in return and yield statements (gh-4509 Sep 22, 2018
Include bpo-32892: Use ast.Constant instead of specific constant AST types. (G… Sep 27, 2018
Lib bpo-34974: Do not replace unexpected errors in bytes() and bytearray(… Oct 14, 2018
Mac bpo-34405: Update to OpenSSL 1.1.0i for macOS installer builds (GH-9166) Sep 11, 2018
Misc bpo-34974: Do not replace unexpected errors in bytes() and bytearray(… Oct 14, 2018
Modules bpo-34941: Fix searching Element subclasses. (GH-9766) Oct 14, 2018
Objects bpo-34974: Do not replace unexpected errors in bytes() and bytearray(… Oct 14, 2018
PC bpo-34770: Fix a possible null pointer dereference in pyshellext.cpp (G… Sep 25, 2018
PCbuild bpo-25711: Rewrite zipimport in pure Python. (GH-6809) Sep 18, 2018
Parser bpo-32892: Use ast.Constant instead of specific constant AST types. (G… Sep 27, 2018
Programs Revert "bpo-34589: Add -X coerce_c_locale command line option (GH-9378)… Sep 19, 2018
Python bpo-34939: Allow annotated global names in module namespace (GH-9844) Oct 14, 2018
Tools Fixes issues in Windows release upload script (GH-9845) Oct 13, 2018
m4 closes bpo-34585: Don't do runtime test to get float byte order. (GH-… Sep 19, 2018
.gitattributes gitattribute: Mark generated files (GH-7619) Jun 15, 2018
.gitignore Add mypy cache to gitignore (GH-6614) Apr 30, 2018
.travis.yml Pin again sphinx version as stated in the comment. (GH-9824) Oct 12, 2018 Convert code of conduct to markdown for Github (GH-9776) Oct 10, 2018
LICENSE advance copyright years to 2018 (#5094) Jan 5, 2018 closes bpo-34869: Remove LDLAST. (GH-9667) Oct 4, 2018
README.rst Update Azure Pipelines badge (GH-9529) Sep 24, 2018
aclocal.m4 run autoconf (GH-9411) Sep 19, 2018
config.guess bpo-33393: Update config.guess and config.sub files (#6658) Apr 30, 2018
config.sub bpo-33393: Update config.guess and config.sub files (#6658) Apr 30, 2018
configure closes bpo-34869: Remove LDLAST. (GH-9667) Oct 4, 2018 closes bpo-34869: Remove LDLAST. (GH-9667) Oct 4, 2018
install-sh Patch #746366: Update to current automake install-sh. Will backport t… Jun 14, 2003 bpo-31425: Expose AF_QIPCRTR in socket module (GH-3706) Sep 26, 2018 bpo-29442: Replace optparse with argparse in (GH-139) Jul 11, 2018


This is Python version 3.8.0 alpha 0

CPython build status on Travis CI CPython build status on Appveyor CPython build status on Azure DevOps CPython code coverage on Codecov Python Zulip chat

Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018 Python Software Foundation. All rights reserved.

See the end of this file for further copyright and license information.

General Information

Contributing to CPython

For more complete instructions on contributing to CPython development, see the Developer Guide.

Using Python

Installable Python kits, and information about using Python, are available at

Build Instructions

On Unix, Linux, BSD, macOS, and Cygwin:

make test
sudo make install

This will install Python as python3.

You can pass many options to the configure script; run ./configure --help to find out more. On macOS and Cygwin, the executable is called python.exe; elsewhere it's just python.

If you are running on macOS with the latest updates installed, make sure to install openSSL or some other SSL software along with Homebrew or another package manager. If issues persist, see for more information.

On macOS, if you have configured Python with --enable-framework, you should use make frameworkinstall to do the installation. Note that this installs the Python executable in a place that is not normally on your PATH, you may want to set up a symlink in /usr/local/bin.

On Windows, see PCbuild/readme.txt.

If you wish, you can create a subdirectory and invoke configure from there. For example:

mkdir debug
cd debug
../configure --with-pydebug
make test

(This will fail if you also built at the top-level directory. You should do a make clean at the toplevel first.)

To get an optimized build of Python, configure --enable-optimizations before you run make. This sets the default make targets up to enable Profile Guided Optimization (PGO) and may be used to auto-enable Link Time Optimization (LTO) on some platforms. For more details, see the sections below.

Profile Guided Optimization

PGO takes advantage of recent versions of the GCC or Clang compilers. If used, either via configure --enable-optimizations or by manually running make profile-opt regardless of configure flags, the optimized build process will perform the following steps:

The entire Python directory is cleaned of temporary files that may have resulted from a previous compilation.

An instrumented version of the interpreter is built, using suitable compiler flags for each flavour. Note that this is just an intermediary step. The binary resulting from this step is not good for real life workloads as it has profiling instructions embedded inside.

After the instrumented interpreter is built, the Makefile will run a training workload. This is necessary in order to profile the interpreter execution. Note also that any output, both stdout and stderr, that may appear at this step is suppressed.

The final step is to build the actual interpreter, using the information collected from the instrumented one. The end result will be a Python binary that is optimized; suitable for distribution or production installation.

Link Time Optimization

Enabled via configure's --with-lto flag. LTO takes advantage of the ability of recent compiler toolchains to optimize across the otherwise arbitrary .o file boundary when building final executables or shared libraries for additional performance gains.

What's New

We have a comprehensive overview of the changes in the What's New in Python 3.8 document. For a more detailed change log, read Misc/NEWS, but a full accounting of changes can only be gleaned from the commit history.

If you want to install multiple versions of Python see the section below entitled "Installing multiple versions".


Documentation for Python 3.8 is online, updated daily.

It can also be downloaded in many formats for faster access. The documentation is downloadable in HTML, PDF, and reStructuredText formats; the latter version is primarily for documentation authors, translators, and people with special formatting requirements.

For information about building Python's documentation, refer to Doc/README.rst.

Converting From Python 2.x to 3.x

Significant backward incompatible changes were made for the release of Python 3.0, which may cause programs written for Python 2 to fail when run with Python 3. For more information about porting your code from Python 2 to Python 3, see the Porting HOWTO.


To test the interpreter, type make test in the top-level directory. The test set produces some output. You can generally ignore the messages about skipped tests due to optional features which can't be imported. If a message is printed about a failed test or a traceback or core dump is produced, something is wrong.

By default, tests are prevented from overusing resources like disk space and memory. To enable these tests, run make testall.

If any tests fail, you can re-run the failing test(s) in verbose mode. For example, if test_os and test_gdb failed, you can run:

make test TESTOPTS="-v test_os test_gdb"

If the failure persists and appears to be a problem with Python rather than your environment, you can file a bug report and include relevant output from that command to show the issue.

See Running & Writing Tests for more on running tests.

Installing multiple versions

On Unix and Mac systems if you intend to install multiple versions of Python using the same installation prefix (--prefix argument to the configure script) you must take care that your primary python executable is not overwritten by the installation of a different version. All files and directories installed using make altinstall contain the major and minor version and can thus live side-by-side. make install also creates ${prefix}/bin/python3 which refers to ${prefix}/bin/pythonX.Y. If you intend to install multiple versions using the same prefix you must decide which version (if any) is your "primary" version. Install that version using make install. Install all other versions using make altinstall.

For example, if you want to install Python 2.7, 3.6, and 3.8 with 3.8 being the primary version, you would execute make install in your 3.8 build directory and make altinstall in the others.

Issue Tracker and Mailing List

Bug reports are welcome! You can use the issue tracker to report bugs, and/or submit pull requests on GitHub.

You can also follow development discussion on the python-dev mailing list.

Proposals for enhancement

If you have a proposal to change Python, you may want to send an email to the comp.lang.python or python-ideas mailing lists for initial feedback. A Python Enhancement Proposal (PEP) may be submitted if your idea gains ground. All current PEPs, as well as guidelines for submitting a new PEP, are listed at

Release Schedule

See PEP 569 for Python 3.8 release details.

Copyright and License Information

Copyright (c) 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018 Python Software Foundation. All rights reserved.

Copyright (c) 2000 All rights reserved.

Copyright (c) 1995-2001 Corporation for National Research Initiatives. All rights reserved.

Copyright (c) 1991-1995 Stichting Mathematisch Centrum. All rights reserved.

See the file "LICENSE" for information on the history of this software, terms & conditions for usage, and a DISCLAIMER OF ALL WARRANTIES.

This Python distribution contains no GNU General Public License (GPL) code, so it may be used in proprietary projects. There are interfaces to some GNU code but these are entirely optional.

All trademarks referenced herein are property of their respective holders.