New source-only versions can be released as needed. end-of-life: Five years after a release, support ends. The release cycle is frozen; no further changes are allowed. See also the …

The Status of Python versions page contains list of active and end-of-life branches. The latest release for each Python version can be found on the download page.

Within the GitHub Python organization, repositories are expected to relate to the Python language, the CPython reference implementation, their documentation and their development …

For Python code you should follow PEP 8, and for C code you should follow PEP 7. If you have one or two discrepancies those can be fixed by the core team member who merges your pull …

This guide is a comprehensive resource for contributing to Python – for both new and experienced contributors. It is maintained by the same community that maintains Python.

Following Python’s development- Standards of behaviour in these communication channels, Mailing lists, Discourse (discuss.python.org web forum)- Tutorials for new users, Reading …

Reviewing How to review a pull request Leaving a pull request review on GitHub Dismissing review from another core team member Keeping continuous integration green Update branch …

Can I keep it? What hierarchy should I use in my GitHub repository? Which version of the Python documentation should be translated? The entry for my translation is missing or not up to date …

For a concise step by step summary of building Python on Windows, you can read Victor Stinner’s guide. All supported versions of Python can be built using Microsoft Visual Studio 2017 or …

The CPython code base is constantly changing and evolving. Here’s a sample of references about CPython’s architecture aimed at building your understanding of CPython internals and its …