Newest Python PEPs
https://peps.python.org/
Newest Python Enhancement Proposals (PEPs): Information on new language features and some meta-information like release procedure and schedules.https://cyber.harvard.edu/rss/rss.htmlenWed, 07 Jan 2026 15:14:51 GMTPEP 822: Dedented Multiline String (d-string)
https://peps.python.org/pep-0822/
This PEP proposes to add a feature that automatically removes indentation from multiline string literals.Inada Naoki (songofacandy@gmail.com)https://peps.python.org/pep-0822/Mon, 05 Jan 2026 00:00:00 GMTPEP 820: PySlot: Unified slot system for the C API
https://peps.python.org/pep-0820/
Replace type and module slots with a new, more type-safe structure that allows adding new slots in a more forward-compatible way.Petr Viktorin (encukou@gmail.com)https://peps.python.org/pep-0820/Fri, 19 Dec 2025 00:00:00 GMTPEP 819: JSON Package Metadata
https://peps.python.org/pep-0819/
This PEP proposes introducing JSON encoded core metadata and wheel file format metadata files in Python packages. Python package metadata (“core metadata”) was first defined in PEP 241 to use RFC 822 email headers to encode information about packages. This was reasonable in 2001; email messages were the only widely used, standardized text format that had a parser in the standard library. However, issues with handling different encodings, differing handling of line breaks, and other differences between implementations have caused numerous packaging bugs. Using the JSON format for encoding metadata files would eliminate a wide range of these potential issues.Emma Harper Smith (emma@python.org)https://peps.python.org/pep-0819/Thu, 18 Dec 2025 00:00:00 GMTPEP 815: Deprecate “RECORD.jws“ and “RECORD.p7s“
https://peps.python.org/pep-0815/
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.Konstantin Schütze (konstin@mailbox.org), William Woodruff (william@yossarian.net)https://peps.python.org/pep-0815/Thu, 04 Dec 2025 00:00:00 GMTPEP 814: Add frozendict built-in type
https://peps.python.org/pep-0814/
A new public immutable type frozendict is added to the builtins module.Victor Stinner (vstinner@python.org), Donghee Na (donghee.na@python.org)https://peps.python.org/pep-0814/Wed, 12 Nov 2025 00:00:00 GMTPEP 816: WASI Support
https://peps.python.org/pep-0816/
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.Brett Cannon (brett@python.org)https://peps.python.org/pep-0816/Wed, 05 Nov 2025 00:00:00 GMTPEP 811: Defining Python Security Response Team membership and responsibilities
https://peps.python.org/pep-0811/
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.Seth Michael Larson (seth@python.org)https://peps.python.org/pep-0811/Wed, 22 Oct 2025 00:00:00 GMTPEP 8107: 2026 Term Steering Council election
https://peps.python.org/pep-8107/
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).Ee Durbin (ee@python.org)https://peps.python.org/pep-8107/Tue, 21 Oct 2025 00:00:00 GMTPEP 810: Explicit lazy imports
https://peps.python.org/pep-0810/
This PEP introduces syntax for lazy imports as an explicit language feature:Pablo Galindo Salgado (pablogsal@python.org), Germán Méndez Bravo (german.mb@gmail.com), Thomas Wouters (thomas@python.org), Dino Viehland (dinoviehland@gmail.com), Brittany Reynoso (brittanyrey@gmail.com), Noah Kim (noahbkim@gmail.com), Tim Stumbaugh (me@tjstum.com)https://peps.python.org/pep-0810/Thu, 02 Oct 2025 00:00:00 GMTPEP 809: Stable ABI for the Future
https://peps.python.org/pep-0809/
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 with the preceding one.Steve Dower (steve.dower@python.org)https://peps.python.org/pep-0809/Fri, 19 Sep 2025 00:00:00 GMT