Newest Python PEPs
Newest Python Enhancement Proposals (PEPs): Information on new language features and some meta-information like release procedure and schedules.
- Website
- python.org · all feeds from this site
- Feed URL
https://www.python.org/dev/peps/peps.rss/
Read it in your FeedListing reader
Or add to: Feedly Inoreader Raw feed
Latest posts
-
PEP 851: Add list.discard()
Add list.discard(x), which removes the first item equal to x if one is present and does nothing otherwise, returning whether an item was removed. It is the non-raising counterpart to list.remove(), which currently has none. The name is taken from set.discard(), which already…
-
PEP 850: Wheel Variants: Providers
This PEP extends PEP 825 by defining how variant properties are governed and how their compatibility is determined. This is done either via static feature and feature value compatibility lists specified in the variant metadata, or by querying opt-in plugins that are Python…
-
PEP 849: More Expressive Type Expressions
Currently, the Python interpreter allows any expression to be used as an annotation. But their most popular usage, type annotations, are restricted to only a small subset of possible expressions. This is because type annotations need to be introspectable at runtime and many…
-
PEP 824: None-coalescing operators
This PEP proposes adding two new operators.
-
PEP 823: None-aware access operators
This PEP proposes adding two new operators.
-
PEP 848: Generational Incremental Garbage Collection
This PEP proposes adding a new cyclic garbage collector to CPython. The new collector will be both generational and incremental. Collections will alternate: a young collection, then an (incremental) old collection, then a young collection, and so on.
-
PEP 846: Docstrings for Type Aliases
This PEP proposes preserving a string literal immediately following a type statement as the resulting type alias object’s __doc__ attribute, exposing that documentation through ast, and displaying it through pydoc and help(). It follows the placement already supported by…
-
PEP 845: Leading-Dot Value Patterns
This PEP enables the use of non-attribute names as value patterns in match statements. A name prefixed with a dot is looked up using the normal name resolution rules and compared to the match subject by equality in the same manner as existing value patterns, instead of being…
-
PEP 847: Problem Details for the Simple Repository API
This PEP proposes standardizing the format of error responses returned by the simple repository API.