This PEP proposes allowing Unpack[TypedDict] in the parameter list inside Callable, enabling concise and type-safe ways to describe keyword-only callable signatures. Currently, Callable assumes positional-only parameters, and typing keyword-only functions requires verbose callback protocols. With...

   This PEP proposes to add a feature that automatically removes indentation from multiline string literals.

   Replace type and module slots with a new structure: a tagged anonymous union with flags. This improves type safety and allows adding new slots in a more forward-compatible way.

   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...

   Pyodide is a distribution of Python for JavaScript runtimes, including browsers. Browsers are a universal computing platform. As with C for Unix family operating systems, in the browser platform all fundamental capabilities are exposed through the JavaScript language. For years, Pyodide has...

   Python’s existing wheel packaging format uses packaging:specifications platform-compatibility-tags to specify a given wheel’s supported environments. These tags are unable to express modern hardware configurations and their features, such as the availability of GPU acceleration. The tags fail to...

   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.