Managing changes for CPython, for configuring and compiling it on z/OS, and other minor bugfixes to be submitted to upstream.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
David Lanzendörfer 59e7fa51a0 Finally got atomics working 9 months ago
.azure-pipelines bpo-46106: Update OpenSSL to 1.1.1m (GH-30211) (GH-30224) 12 months ago
.github bpo-46106: Update OpenSSL to 1.1.1m (GH-30211) (GH-30224) 12 months ago
Doc Define Py_BUILD_CORE_MODULE 11 months ago
Grammar [3.10] bpo-45727: Only trigger the 'did you forgot a comma' error suggestion if inside parentheses. (GH-29767) 1 year ago
Include Finally got atomics working 9 months ago
Lib Python 3.10.2 11 months ago
Mac bpo-40477: macOS Python Launcher app fixes for recent macOS releases (GH-30348) (GH-30349) 11 months ago
Misc Python 3.10.2 11 months ago
Modules Thread ID size and access 10 months ago
Objects OS/390: Parser now working 9 months ago
PC [3.10] Update copyright year to 2022. (GH-30335) (GH-30336) 11 months ago
PCbuild bpo-46106: Update OpenSSL to 1.1.1m (GH-30211) (GH-30224) 12 months ago
Parser OS/390: Parser now working 9 months ago
Programs OS/390: Parser now working 9 months ago
Python OS/390: Parser now working 9 months ago
Tools bpo-46106: Update OpenSSL to 1.1.1m (GH-30211) (GH-30224) 12 months ago
.editorconfig bpo-44854: Add .editorconfig file to help enforce `make patchcheck` (GH-27638) 1 year ago
.gitattributes bpo-43244: Remove ast.h, asdl.h, Python-ast.h headers (GH-24933) 2 years ago
.gitignore [3.10] bpo-44035: Check autoconf files thoroughly (GH-29935) (GH-29937) 1 year ago
.travis.yml [3.10] Fail the CI if an optional module fails to compile (GH-27466). (GH-27481) 1 year ago Fix markup and minor grammar improvements in (GH-13640) 4 years ago
LICENSE [3.10] Update copyright year to 2022. (GH-30335) (GH-30336) 11 months ago Having it separate doesn't work 10 months ago
README.rst Python 3.10.2 11 months ago
aclocal.m4 WIP: Compiles now but... 10 months ago
config.guess [3.10] bpo-33393: Update config.guess and config.sub (GH-29781) (GH-29782) 1 year ago
config.sub [3.10] bpo-33393: Update config.guess and config.sub (GH-29781) (GH-29782) 1 year ago
configure OS/390: Parser now working 9 months ago OS/390: Parser now working 9 months ago
install-sh bpo-34765: install-sh is executable (GH-10225) 4 years ago
netlify.toml bpo-37860: Add netlify deploy preview for docs (GH-15288) 3 years ago OS/390: Parser now working 9 months ago [3.10] bpo-45881: Use CC from env first for cross building (GH-29752). (GH-29753) 1 year ago


This is Python version 3.10.2

.. image::
:alt: CPython build status on Travis CI

.. image::
:alt: CPython build status on GitHub Actions

.. image::
:alt: CPython build status on Azure DevOps

.. image::
:alt: Python Discourse chat

Copyright (c) 2001-2022 Python Software Foundation. All rights reserved.

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

.. contents::

General Information

- Website:
- Source code:
- Issue tracker:
- Documentation:
- Developer's Guide:

Contributing to CPython

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

.. _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 case-insensitive file systems and on Cygwin,
the executable is called ``python.exe``; elsewhere it's just ``python``.

Building a complete Python installation requires the use of various
additional third-party libraries, depending on your build platform and
configure options. Not all standard library modules are buildable or
useable on all platforms. Refer to the
`Install dependencies <>`_
section of the `Developer Guide`_ for current detailed information on
dependencies for various Linux distributions and macOS.

On macOS, there are additional configure and build options related
to macOS framework and universal builds. Refer to `Mac/README.rst

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 top-level 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

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 flavor. 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's 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.10 <>`_ 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.10 <>`_ 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.10 with 3.10 being the
primary version, you would execute ``make install`` in your 3.10 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
` <>`_.

.. _python-ideas:
.. _comp.lang.python:

Release Schedule

See :pep:`619` for Python 3.10 release details.

Copyright and License Information

Copyright (c) 2001-2022 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 `LICENSE <>`_ for
information on the history of this software, terms & conditions for usage, and a

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.