The main branch is currently the future Python 3.15, and is the only branch that accepts new features. The latest release for each Python version can be found on the download page.

The Python Steering Council has overall authority over Python and has delegated some of its responsibilities to other groups. This table lists the PEPs defining each group’s responsibilities, …

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.

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.

Development cycle Adding to the stdlib Standard library extension modules Changing Python’s C API Changing CPython’s grammar Porting to a new platform Software Bill-of-Materials (SBOM)

The existing Lifecycle of a pull request page is long and includes many details. Some only apply to code contributions, but many are common to all contributions.

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

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

Lifecycle of a pull request Introduction Quick guide Don’t force-push Step-by-step guide Resolving merge conflicts Making good PRs Copyrights patchcheck Making good commits Licensing …