1
PEP 634 – Structural Pattern Matching: Specification
This PEP provides the technical specification for the match statement. It replaces PEP 622, which is hereby split in three parts:
Python.org
The official home of the Python Programming Language
- Popular posts
- 50
- Total points
- 7,690
- HN comments
- 3,309
- Rank
- #127 company
Visit python.org → RSS feedOn Hacker News Nov 2007 – Oct 2026
2
PEP 518 – Specifying Minimum Build System Requirements for Python Projects
This PEP specifies how Python software packages should specify what build dependencies they have in order to execute their chosen build system. As part of this specification, a new configuration file is introduced for software packages to use to specify...
3
PEP 20 – The Zen of Python
Long time Pythoneer Tim Peters succinctly channels the BDFL’s guiding principles for Python’s design into 20 aphorisms, only 19 of which have been written down.
4
PEP 554 – Multiple Interpreters in the Stdlib
CPython has supported multiple interpreters in the same process (AKA “subinterpreters”) since version 1.5 (1997). The feature has been available via the C-API. [c-api] Multiple interpreters operate in relative isolation from one another, which facilit...
5
PEP 3131 – Supporting Non-ASCII Identifiers
This PEP suggests to support non-ASCII letters (such as accented characters, Cyrillic, Greek, Kanji, etc.) in Python identifiers.
6
PEP 636 – Structural Pattern Matching: Tutorial
This PEP is a tutorial for the pattern matching introduced by PEP 634.
7
PEP 3113 – Removal of Tuple Parameter Unpacking
Tuple parameter unpacking is the use of a tuple as a parameter in a function signature so as to have a sequence argument automatically unpacked. An example is:
8
PEP 289 – Generator Expressions
This PEP introduces generator expressions as a high performance, memory efficient generalization of list comprehensions PEP 202 and generators PEP 255.
9
PEP 557 – Data Classes
This PEP describes an addition to the standard library called Data Classes. Although they use a very different mechanism, Data Classes can be thought of as “mutable namedtuples with defaults”. Because Data Classes use normal class definition syntax, y...
10
PEP 394 – The “python” Command on Unix-Like Systems
This PEP outlines the behavior of Python scripts when the python command is invoked. Depending on a distribution or system configuration, python may or may not be installed. If python is installed its target interpreter may refer to python2 or python3. ...
11
PEP 8 – Style Guide for Python Code
This document gives coding conventions for the Python code comprising the standard library in the main Python distribution. Please see the companion informational PEP describing style guidelines for the C code in the C implementation of Python.
12
PEP 572 – Assignment Expressions
This is a proposal for creating a way to assign to variables within an expression using the notation NAME := expr.
13
PEP 374 – Choosing a distributed VCS for the Python project
Python Enhancement Proposals (PEPs)
14
PEP 3104 – Access to Names in Outer Scopes
In most languages that support nested scopes, code can refer to or rebind (assign to) any name in the nearest enclosing scope. Currently, Python code can refer to a name in any enclosing scope, but it can only rebind names in two scopes: the local scope...
15
PEP 373 – Python 2.7 Release Schedule
This document describes the development and release schedule for Python 2.7.
16
PEP 393 – Flexible String Representation
The Unicode string type is changed to support multiple internal representations, depending on the character with the largest Unicode ordinal (1, 2, or 4 bytes). This will allow a space-efficient representation in common cases, but give access to full UC...
17
PEP 318 – Decorators for Functions and Methods
The current method for transforming functions and methods (for instance, declaring them as a class or static method) is awkward and can lead to code that is difficult to understand. Ideally, these transformations should be made at the same point in the...
18
PEP 3146 – Merging Unladen Swallow into CPython
This PEP proposes the merger of the Unladen Swallow project 3 into CPython’s source tree. Unladen Swallow is an open-source branch of CPython focused on performance. Unladen Swallow is source-compatible with valid Python 2.6.4 applications and C extensi...
19
PEP 263 – Defining Python Source Code Encodings
This PEP proposes to introduce a syntax to declare the encoding of a Python source file. The encoding information is then used by the Python parser to interpret the file using the given encoding. Most notably this enhances the interpretation of Unicode ...
20
PEP 3107 – Function Annotations
This PEP introduces a syntax for adding arbitrary metadata annotations to Python functions 1.
21
PEP 635 – Structural Pattern Matching: Motivation and Rationale
This PEP provides the motivation and rationale for PEP 634 (“Structural Pattern Matching: Specification”). First-time readers are encouraged to start with PEP 636, which provides a gentler introduction to the concepts, syntax and semantics of patterns.