This PEP deprecates the RECORD.jws and RECORD.p7s wheel signature files. Lack of support in tooling means that these virtually unused files do not provide the security they purport. Users looking for wheel signing should instead refer to index hosted attestations.

   A new public immutable type frozendict is added to the builtins module.

   This PEP outlines the expected support for WASI by CPython. It contains enough details to know what WASI and WASI SDK version is expected to be supported for any release of CPython while official WASI support is specified in PEP 11.

   This PEP proposes formalizing the membership and responsibilities policies of the Python Security Response Team (PSRT). The PSRT is a highly trusted cabal of Python developers which handles security vulnerability disclosures to the security python.org mailing list.

   This document describes the schedule and other details of the 2025 election for the Python steering council, as specified in PEP 13. This is the steering council election for the 2026 term (i.e. Python 3.15).

   This PEP introduces syntax for lazy imports as an explicit language feature:

   The Stable ABI as abi3 can no longer be preserved, and requires replacement. abi2026 will be the first replacement, providing resolution of current known incompatibilities, with planned retirement after at least 10 years. The next ABI (for example, abi2031) will have at least five years of overlap...

   This PEP relaxes the constraint on dynamic metadata listed in the [project] section in pyproject.toml. It is now permitted to define a static portion of a dynamic metadata field in the [project] table as long as the field is a table or array.

   This PEP proposes a standard mechanism through which arbitrary Python package indices can support Trusted Publishing, a misuse-resistant credential exchange scheme already implemented by the Python Package Index (PyPI).

   Python allows the with and async with statements to handle multiple context managers in a single statement, so long as they are all respectively synchronous or asynchronous. When mixing synchronous and asynchronous context managers, developers must use deeply nested statements or use risky...