text stringlengths 330 67k | status stringclasses 9
values | title stringlengths 18 80 | type stringclasses 3
values | abstract stringlengths 4 917 |
|---|---|---|---|---|
PEP 476 – Enabling certificate verification by default for stdlib http clients
Author:
Alex Gaynor <alex.gaynor at gmail.com>
Status:
Final
Type:
Standards Track
Created:
28-Aug-2014
Python-Version:
2.7.9, 3.4.3, 3.5
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Technical Details
Trust databa... | Final | PEP 476 – Enabling certificate verification by default for stdlib http clients | Standards Track | Currently when a standard library http client (the urllib, urllib2,
http, and httplib modules) encounters an https:// URL it will wrap
the network HTTP traffic in a TLS stream, as is necessary to communicate with
such a server. However, during the TLS handshake it will not actually check
that the server has an X509 cer... |
PEP 478 – Python 3.5 Release Schedule
Author:
Larry Hastings <larry at hastings.org>
Status:
Final
Type:
Informational
Topic:
Release
Created:
22-Sep-2014
Python-Version:
3.5
Table of Contents
Abstract
Release Manager and Crew
Release Schedule
Features for 3.5
Copyright
Abstract
This document describes the deve... | Final | PEP 478 – Python 3.5 Release Schedule | Informational | This document describes the development and release schedule for
Python 3.5. The schedule primarily concerns itself with PEP-sized
items. |
PEP 479 – Change StopIteration handling inside generators
Author:
Chris Angelico <rosuav at gmail.com>, Guido van Rossum <guido at python.org>
Status:
Final
Type:
Standards Track
Created:
15-Nov-2014
Python-Version:
3.5
Post-History:
15-Nov-2014, 19-Nov-2014, 05-Dec-2014
Table of Contents
Abstract
Acceptance
Ratio... | Final | PEP 479 – Change StopIteration handling inside generators | Standards Track | This PEP proposes a change to generators: when StopIteration is
raised inside a generator, it is replaced with RuntimeError.
(More precisely, this happens when the exception is about to bubble
out of the generator’s stack frame.) Because the change is backwards
incompatible, the feature is initially introduced using a... |
PEP 481 – Migrate CPython to Git, Github, and Phabricator
Author:
Donald Stufft <donald at stufft.io>
Status:
Withdrawn
Type:
Process
Created:
29-Nov-2014
Post-History:
29-Nov-2014
Table of Contents
Abstract
Rationale
Version Control System
Repository Hosting
Code Review
GitHub Pull Requests
Phabricator
Critic... | Withdrawn | PEP 481 – Migrate CPython to Git, Github, and Phabricator | Process | Note |
PEP 485 – A Function for testing approximate equality
Author:
Christopher Barker <PythonCHB at gmail.com>
Status:
Final
Type:
Standards Track
Created:
20-Jan-2015
Python-Version:
3.5
Post-History:
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Existing Implementations
Proposed Implementatio... | Final | PEP 485 – A Function for testing approximate equality | Standards Track | This PEP proposes the addition of an isclose() function to the standard
library math module that determines whether one value is approximately equal
or “close” to another value. |
PEP 486 – Make the Python Launcher aware of virtual environments
Author:
Paul Moore <p.f.moore at gmail.com>
Status:
Final
Type:
Standards Track
Created:
12-Feb-2015
Python-Version:
3.5
Post-History:
12-Feb-2015
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Implementation
Impact on Script Lau... | Final | PEP 486 – Make the Python Launcher aware of virtual environments | Standards Track | The Windows installers for Python include a launcher that locates the
correct Python interpreter to run (see PEP 397). However, the
launcher is not aware of virtual environments (virtualenv [1] or PEP
405 based), and so cannot be used to run commands from the active
virtualenv. |
PEP 487 – Simpler customisation of class creation
Author:
Martin Teichmann <lkb.teichmann at gmail.com>
Status:
Final
Type:
Standards Track
Created:
27-Feb-2015
Python-Version:
3.6
Post-History:
27-Feb-2015, 05-Feb-2016, 24-Jun-2016, 02-Jul-2016, 13-Jul-2016
Replaces:
422
Resolution:
Python-Dev message
Table of Co... | Final | PEP 487 – Simpler customisation of class creation | Standards Track | Currently, customising class creation requires the use of a custom metaclass.
This custom metaclass then persists for the entire lifecycle of the class,
creating the potential for spurious metaclass conflicts. |
PEP 488 – Elimination of PYO files
Author:
Brett Cannon <brett at python.org>
Status:
Final
Type:
Standards Track
Created:
20-Feb-2015
Python-Version:
3.5
Post-History:
06-Mar-2015,
13-Mar-2015,
20-Mar-2015
Table of Contents
Abstract
Rationale
Proposal
Implementation
importlib
Rest of the standard library
Compat... | Final | PEP 488 – Elimination of PYO files | Standards Track | This PEP proposes eliminating the concept of PYO files from Python.
To continue the support of the separation of bytecode files based on
their optimization level, this PEP proposes extending the PYC file
name to include the optimization level in the bytecode repository
directory when there are optimizations applied. |
PEP 490 – Chain exceptions at C level
Author:
Victor Stinner <vstinner at python.org>
Status:
Rejected
Type:
Standards Track
Created:
25-Mar-2015
Python-Version:
3.6
Table of Contents
Abstract
Rationale
Proposal
Modify PyErr_*() functions to chain exceptions
Modify functions to not chain exceptions
Modify function... | Rejected | PEP 490 – Chain exceptions at C level | Standards Track | Chain exceptions at C level, as already done at Python level. |
PEP 494 – Python 3.6 Release Schedule
Author:
Ned Deily <nad at python.org>
Status:
Final
Type:
Informational
Topic:
Release
Created:
30-May-2015
Python-Version:
3.6
Table of Contents
Abstract
Release Manager and Crew
3.6 Lifespan
Release Schedule
3.6.0 schedule
3.6.1 schedule (first bugfix release)
3.6.2 schedule... | Final | PEP 494 – Python 3.6 Release Schedule | Informational | This document describes the development and release schedule for
Python 3.6. The schedule primarily concerns itself with PEP-sized
items. |
PEP 498 – Literal String Interpolation
Author:
Eric V. Smith <eric at trueblade.com>
Status:
Final
Type:
Standards Track
Created:
01-Aug-2015
Python-Version:
3.6
Post-History:
07-Aug-2015, 30-Aug-2015, 04-Sep-2015, 19-Sep-2015, 06-Nov-2016
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
No use ... | Final | PEP 498 – Literal String Interpolation | Standards Track | Python supports multiple ways to format text strings. These include
%-formatting [1], str.format() [2], and string.Template
[3]. Each of these methods have their advantages, but in addition
have disadvantages that make them cumbersome to use in practice. This
PEP proposed to add a new string formatting mechanism: Liter... |
PEP 501 – General purpose string interpolation
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Deferred
Type:
Standards Track
Requires:
498
Created:
08-Aug-2015
Python-Version:
3.6
Post-History:
08-Aug-2015, 23-Aug-2015, 30-Aug-2015
Table of Contents
Abstract
PEP Deferral
Summary of differences from PEP 498... | Deferred | PEP 501 – General purpose string interpolation | Standards Track | PEP 498 proposes new syntactic support for string interpolation that is
transparent to the compiler, allow name references from the interpolation
operation full access to containing namespaces (as with any other expression),
rather than being limited to explicit name references. These are referred
to in the PEP as “f-s... |
PEP 502 – String Interpolation - Extended Discussion
Author:
Mike G. Miller
Status:
Rejected
Type:
Informational
Created:
10-Aug-2015
Python-Version:
3.6
Table of Contents
Abstract
PEP Status
Motivation
Rationale
Goals
Limitations
Background
Printf-style formatting, via operator
string.Template Class
PEP 215 - Str... | Rejected | PEP 502 – String Interpolation - Extended Discussion | Informational | PEP 498: Literal String Interpolation, which proposed “formatted strings” was
accepted September 9th, 2015.
Additional background and rationale given during its design phase is detailed
below. |
PEP 504 – Using the System RNG by default
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Withdrawn
Type:
Standards Track
Created:
15-Sep-2015
Python-Version:
3.6
Post-History:
15-Sep-2015
Table of Contents
Abstract
PEP Withdrawal
Proposal
Warning on implicit opt-in
Performance impact
Documentation changes
... | Withdrawn | PEP 504 – Using the System RNG by default | Standards Track | Python currently defaults to using the deterministic Mersenne Twister random
number generator for the module level APIs in the random module, requiring
users to know that when they’re performing “security sensitive” work, they
should instead switch to using the cryptographically secure os.urandom or
random.SystemRandom... |
PEP 505 – None-aware operators
Author:
Mark E. Haase <mehaase at gmail.com>, Steve Dower <steve.dower at python.org>
Status:
Deferred
Type:
Standards Track
Created:
18-Sep-2015
Python-Version:
3.8
Table of Contents
Abstract
Syntax and Semantics
Specialness of None
Grammar changes
The coalesce rule
The maybe-dot an... | Deferred | PEP 505 – None-aware operators | Standards Track | Several modern programming languages have so-called “null-coalescing” or
“null- aware” operators, including C# [1], Dart [2], Perl, Swift, and PHP
(starting in version 7). There are also stage 3 draft proposals for their
addition to ECMAScript (a.k.a. JavaScript) [3] [4]. These operators provide
syntactic sugar for com... |
PEP 506 – Adding A Secrets Module To The Standard Library
Author:
Steven D’Aprano <steve at pearwood.info>
Status:
Final
Type:
Standards Track
Created:
19-Sep-2015
Python-Version:
3.6
Post-History:
Table of Contents
Abstract
Definitions
Rationale
Proposal
API and Implementation
Default arguments
Naming convention... | Final | PEP 506 – Adding A Secrets Module To The Standard Library | Standards Track | This PEP proposes the addition of a module for common security-related
functions such as generating tokens to the Python standard library. |
PEP 507 – Migrate CPython to Git and GitLab
Author:
Barry Warsaw <barry at python.org>
Status:
Rejected
Type:
Process
Created:
30-Sep-2015
Post-History:
Resolution:
Core-Workflow message
Table of Contents
Abstract
Rationale
Version Control System
Repository Hosting
Code Review
GitLab merge requests
Criticism
X ... | Rejected | PEP 507 – Migrate CPython to Git and GitLab | Process | This PEP proposes migrating the repository hosting of CPython and the
supporting repositories to Git. Further, it proposes adopting a
hosted GitLab instance as the primary way of handling merge requests,
code reviews, and code hosting. It is similar in intent to PEP 481
but proposes an open source alternative to GitH... |
PEP 509 – Add a private version to dict
Author:
Victor Stinner <vstinner at python.org>
Status:
Superseded
Type:
Standards Track
Created:
04-Jan-2016
Python-Version:
3.6
Post-History:
08-Jan-2016,
11-Jan-2016,
14-Apr-2016,
19-Apr-2016
Superseded-By:
699
Resolution:
Python-Dev message
Table of Contents
Abstract
Rat... | Superseded | PEP 509 – Add a private version to dict | Standards Track | Add a new private version to the builtin dict type, incremented at
each dictionary creation and at each dictionary change, to implement
fast guards on namespaces. |
PEP 510 – Specialize functions with guards
Author:
Victor Stinner <vstinner at python.org>
Status:
Rejected
Type:
Standards Track
Created:
04-Jan-2016
Python-Version:
3.6
Table of Contents
Rejection Notice
Abstract
Rationale
Python semantics
Why not a JIT compiler?
Examples
Hypothetical myoptimizer module
Using ... | Rejected | PEP 510 – Specialize functions with guards | Standards Track | Add functions to the Python C API to specialize pure Python functions:
add specialized codes with guards. It allows to implement static
optimizers respecting the Python semantics. |
PEP 511 – API for code transformers
Author:
Victor Stinner <vstinner at python.org>
Status:
Rejected
Type:
Standards Track
Created:
04-Jan-2016
Python-Version:
3.6
Table of Contents
Rejection Notice
Abstract
Rationale
Usage 1: AST optimizer
Usage 2: Preprocessor
Usage 3: Disable all optimization
Usage 4: Write new... | Rejected | PEP 511 – API for code transformers | Standards Track | Propose an API to register bytecode and AST transformers. Add also -o
OPTIM_TAG command line option to change .pyc filenames, -o
noopt disables the peephole optimizer. Raise an ImportError
exception on import if the .pyc file is missing and the code
transformers required to transform the code are missing. code
transfo... |
PEP 519 – Adding a file system path protocol
Author:
Brett Cannon <brett at python.org>,
Koos Zevenhoven <k7hoven at gmail.com>
Status:
Final
Type:
Standards Track
Created:
11-May-2016
Python-Version:
3.6
Post-History:
11-May-2016,
12-May-2016,
13-May-2016
Resolution:
Python-Dev message
Table of Contents
Abstract
... | Final | PEP 519 – Adding a file system path protocol | Standards Track | This PEP proposes a protocol for classes which represent a file system
path to be able to provide a str or bytes representation.
Changes to Python’s standard library are also proposed to utilize this
protocol where appropriate to facilitate the use of path objects where
historically only str and/or bytes file system pa... |
PEP 520 – Preserving Class Attribute Definition Order
Author:
Eric Snow <ericsnowcurrently at gmail.com>
Status:
Final
Type:
Standards Track
Created:
07-Jun-2016
Python-Version:
3.6
Post-History:
07-Jun-2016, 11-Jun-2016, 20-Jun-2016, 24-Jun-2016
Resolution:
Python-Dev message
Table of Contents
Abstract
Motivation... | Final | PEP 520 – Preserving Class Attribute Definition Order | Standards Track | The class definition syntax is ordered by its very nature. Class
attributes defined there are thus ordered. Aside from helping with
readability, that ordering is sometimes significant. If it were
automatically available outside the class definition then the
attribute order could be used without the need for extra boi... |
PEP 521 – Managing global context via ‘with’ blocks in generators and coroutines
Author:
Nathaniel J. Smith <njs at pobox.com>
Status:
Withdrawn
Type:
Standards Track
Created:
27-Apr-2015
Python-Version:
3.6
Post-History:
29-Apr-2015
Table of Contents
PEP Withdrawal
Abstract
Specification
Nested blocks
Other chang... | Withdrawn | PEP 521 – Managing global context via ‘with’ blocks in generators and coroutines | Standards Track | While we generally try to avoid global state when possible, there
nonetheless exist a number of situations where it is agreed to be the
best approach. In Python, a standard pattern for handling such cases
is to store the global state in global or thread-local storage, and
then use with blocks to limit modifications of... |
PEP 522 – Allow BlockingIOError in security sensitive APIs
Author:
Alyssa Coghlan <ncoghlan at gmail.com>, Nathaniel J. Smith <njs at pobox.com>
Status:
Rejected
Type:
Standards Track
Requires:
506
Created:
16-Jun-2016
Python-Version:
3.6
Resolution:
Security-SIG message
Table of Contents
Abstract
Relationship wit... | Rejected | PEP 522 – Allow BlockingIOError in security sensitive APIs | Standards Track | A number of APIs in the standard library that return random values nominally
suitable for use in security sensitive operations currently have an obscure
operating system dependent failure mode that allows them to return values that
are not, in fact, suitable for such operations. |
PEP 523 – Adding a frame evaluation API to CPython
Author:
Brett Cannon <brett at python.org>,
Dino Viehland <dinov at microsoft.com>
Status:
Final
Type:
Standards Track
Created:
16-May-2016
Python-Version:
3.6
Post-History:
16-May-2016
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Proposal
E... | Final | PEP 523 – Adding a frame evaluation API to CPython | Standards Track | This PEP proposes to expand CPython’s C API [2] to allow for
the specification of a per-interpreter function pointer to handle the
evaluation of frames [5]. This proposal also
suggests adding a new field to code objects [3] to store
arbitrary data for use by the frame evaluation function. |
PEP 524 – Make os.urandom() blocking on Linux
Author:
Victor Stinner <vstinner at python.org>
Status:
Final
Type:
Standards Track
Created:
20-Jun-2016
Python-Version:
3.6
Table of Contents
Abstract
The bug
Original bug
Status in Python 3.5.2
Use Cases
Use Case 1: init script
Use case 1.1: No secret needed
Use ca... | Final | PEP 524 – Make os.urandom() blocking on Linux | Standards Track | Modify os.urandom() to block on Linux 3.17 and newer until the OS
urandom is initialized to increase the security. |
PEP 526 – Syntax for Variable Annotations
Author:
Ryan Gonzalez <rymg19 at gmail.com>, Philip House <phouse512 at gmail.com>, Ivan Levkivskyi <levkivskyi at gmail.com>, Lisa Roach <lisaroach14 at gmail.com>, Guido van Rossum <guido at python.org>
Status:
Final
Type:
Standards Track
Topic:
Typing
Created:
09-Aug-2016
... | Final | PEP 526 – Syntax for Variable Annotations | Standards Track | PEP 484 introduced type hints, a.k.a. type annotations. While its
main focus was function annotations, it also introduced the notion of
type comments to annotate variables: |
PEP 528 – Change Windows console encoding to UTF-8
Author:
Steve Dower <steve.dower at python.org>
Status:
Final
Type:
Standards Track
Created:
27-Aug-2016
Python-Version:
3.6
Post-History:
01-Sep-2016, 04-Sep-2016
Resolution:
Python-Dev message
Table of Contents
Abstract
Specific Changes
Add _io.WindowsConsoleIO
... | Final | PEP 528 – Change Windows console encoding to UTF-8 | Standards Track | Historically, Python uses the ANSI APIs for interacting with the Windows
operating system, often via C Runtime functions. However, these have been long
discouraged in favor of the UTF-16 APIs. Within the operating system, all text
is represented as UTF-16, and the ANSI APIs perform encoding and decoding using
the activ... |
PEP 529 – Change Windows filesystem encoding to UTF-8
Author:
Steve Dower <steve.dower at python.org>
Status:
Final
Type:
Standards Track
Created:
27-Aug-2016
Python-Version:
3.6
Post-History:
01-Sep-2016, 04-Sep-2016
Resolution:
Python-Dev message
Table of Contents
Abstract
Background
Proposal
Specific Changes
Up... | Final | PEP 529 – Change Windows filesystem encoding to UTF-8 | Standards Track | Historically, Python uses the ANSI APIs for interacting with the Windows
operating system, often via C Runtime functions. However, these have been long
discouraged in favor of the UTF-16 APIs. Within the operating system, all text
is represented as UTF-16, and the ANSI APIs perform encoding and decoding using
the activ... |
PEP 531 – Existence checking operators
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Withdrawn
Type:
Standards Track
Created:
25-Oct-2016
Python-Version:
3.7
Post-History:
28-Oct-2016
Table of Contents
Abstract
PEP Withdrawal
Relationship with other PEPs
Rationale
Existence checking expressions
Existence ... | Withdrawn | PEP 531 – Existence checking operators | Standards Track | Inspired by PEP 505 and the related discussions, this PEP proposes the addition
of two new control flow operators to Python: |
PEP 532 – A circuit breaking protocol and binary operators
Author:
Alyssa Coghlan <ncoghlan at gmail.com>,
Mark E. Haase <mehaase at gmail.com>
Status:
Deferred
Type:
Standards Track
Created:
30-Oct-2016
Python-Version:
3.8
Post-History:
05-Nov-2016
Table of Contents
PEP Deferral
Abstract
Relationship with other P... | Deferred | PEP 532 – A circuit breaking protocol and binary operators | Standards Track | Inspired by PEP 335, PEP 505, PEP 531, and the related discussions, this PEP
proposes the definition of a new circuit breaking protocol (using the
method names __then__ and __else__) that provides a common underlying
semantic foundation for: |
PEP 534 – Improved Errors for Missing Standard Library Modules
Author:
Tomáš Orsava <tomas.n at orsava.cz>,
Petr Viktorin <encukou at gmail.com>,
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Deferred
Type:
Standards Track
Created:
05-Sep-2016
Post-History:
Table of Contents
Abstract
PEP Deferral
Motivation
CPyt... | Deferred | PEP 534 – Improved Errors for Missing Standard Library Modules | Standards Track | Python is often being built or distributed without its full standard library.
However, there is as of yet no standard, user friendly way of properly
informing the user about the failure to import such missing standard library
modules. |
PEP 535 – Rich comparison chaining
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Deferred
Type:
Standards Track
Requires:
532
Created:
12-Nov-2016
Python-Version:
3.8
Table of Contents
PEP Deferral
Abstract
Relationship with other PEPs
Specification
Rationale
Implementation
References
Copyright
PEP Def... | Deferred | PEP 535 – Rich comparison chaining | Standards Track | Inspired by PEP 335, and building on the circuit breaking protocol described
in PEP 532, this PEP proposes a change to the definition of chained comparisons,
where the comparison chaining will be updated to use the left-associative
circuit breaking operator (else) rather than the logical disjunction
operator (and) if ... |
PEP 536 – Final Grammar for Literal String Interpolation
Author:
Philipp Angerer <phil.angerer at gmail.com>
Status:
Withdrawn
Type:
Standards Track
Created:
11-Dec-2016
Python-Version:
3.7
Post-History:
18-Aug-2016,
23-Dec-2016,
15-Mar-2019
Resolution:
Discourse message
Table of Contents
Abstract
PEP Withdrawal
T... | Withdrawn | PEP 536 – Final Grammar for Literal String Interpolation | Standards Track | PEP 498 introduced Literal String Interpolation (or “f-strings”).
The expression portions of those literals however are subject to
certain restrictions. This PEP proposes a formal grammar lifting
those restrictions, promoting “f-strings” to “f expressions” or f-literals. |
PEP 537 – Python 3.7 Release Schedule
Author:
Ned Deily <nad at python.org>
Status:
Final
Type:
Informational
Topic:
Release
Created:
23-Dec-2016
Python-Version:
3.7
Table of Contents
Abstract
Release Manager and Crew
3.7 Lifespan
Release Schedule
3.7.0 schedule
3.7.1 schedule (first bugfix release)
3.7.2 schedule... | Final | PEP 537 – Python 3.7 Release Schedule | Informational | This document describes the development and release schedule for
Python 3.7. The schedule primarily concerns itself with PEP-sized
items. |
PEP 542 – Dot Notation Assignment In Function Header
Author:
Markus Meskanen <markusmeskanen at gmail.com>
Status:
Rejected
Type:
Standards Track
Created:
10-Feb-2017
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Implementation
Backwards Compatibility
Copyright
Abstract
Function definition... | Rejected | PEP 542 – Dot Notation Assignment In Function Header | Standards Track | Function definitions only allow simple function names to be used,
even though functions are assignable first class objects. |
PEP 543 – A Unified TLS API for Python
Author:
Cory Benfield <cory at lukasa.co.uk>,
Christian Heimes <christian at python.org>
Status:
Withdrawn
Type:
Standards Track
Created:
17-Oct-2016
Python-Version:
3.7
Post-History:
11-Jan-2017, 19-Jan-2017, 02-Feb-2017, 09-Feb-2017
Table of Contents
Abstract
Resolution
Rat... | Withdrawn | PEP 543 – A Unified TLS API for Python | Standards Track | This PEP would define a standard TLS interface in the form of a collection of
abstract base classes. This interface would allow Python implementations and
third-party libraries to provide bindings to TLS libraries other than OpenSSL
that can be used by tools that expect the interface provided by the Python
standard lib... |
PEP 545 – Python Documentation Translations
Author:
Julien Palard <julien at palard.fr>,
Inada Naoki <songofacandy at gmail.com>,
Victor Stinner <vstinner at python.org>
Status:
Final
Type:
Process
Created:
04-Mar-2017
Resolution:
Python-Dev message
Table of Contents
Abstract
Motivation
Rationale
Translation
Issue... | Final | PEP 545 – Python Documentation Translations | Process | The intent of this PEP is to make existing translations of the Python
Documentation more accessible and discoverable. By doing so, we hope
to attract and motivate new translators and new translations. |
PEP 547 – Running extension modules using the -m option
Author:
Marcel Plch <gmarcel.plch at gmail.com>,
Petr Viktorin <encukou at gmail.com>
Status:
Deferred
Type:
Standards Track
Created:
25-May-2017
Python-Version:
3.7
Post-History:
Table of Contents
Deferral Notice
Abstract
Motivation
Rationale
Background
Pro... | Deferred | PEP 547 – Running extension modules using the -m option | Standards Track | This PEP proposes implementation that allows built-in and extension
modules to be executed in the __main__ namespace using
the PEP 489 multi-phase initialization. |
PEP 548 – More Flexible Loop Control
Author:
R David Murray
Status:
Rejected
Type:
Standards Track
Created:
05-Sep-2017
Python-Version:
3.7
Post-History:
05-Aug-2017
Table of Contents
Rejection Note
Abstract
Motivation
Syntax
Semantics
Justification and Examples
Copyright
Rejection Note
Rejection by Guido:
http... | Rejected | PEP 548 – More Flexible Loop Control | Standards Track | This PEP proposes enhancing the break and continue statements
with an optional boolean expression that controls whether or not
they execute. This allows the flow of control in loops to be
expressed more clearly and compactly. |
PEP 550 – Execution Context
Author:
Yury Selivanov <yury at edgedb.com>,
Elvis Pranskevichus <elvis at edgedb.com>
Status:
Withdrawn
Type:
Standards Track
Created:
11-Aug-2017
Python-Version:
3.7
Post-History:
11-Aug-2017, 15-Aug-2017, 18-Aug-2017, 25-Aug-2017,
01-Sep-2017
Table of Contents
Abstract
PEP Status
Rat... | Withdrawn | PEP 550 – Execution Context | Standards Track | This PEP adds a new generic mechanism of ensuring consistent access
to non-local state in the context of out-of-order execution, such
as in Python generators and coroutines. |
PEP 551 – Security transparency in the Python runtime
Author:
Steve Dower <steve.dower at python.org>
Status:
Withdrawn
Type:
Informational
Created:
23-Aug-2017
Python-Version:
3.7
Post-History:
24-Aug-2017, 28-Aug-2017
Table of Contents
Relationship to PEP 578
Abstract
Background
Summary Recommendations
Restricti... | Withdrawn | PEP 551 – Security transparency in the Python runtime | Informational | This PEP describes the concept of security transparency and how it
applies to the Python runtime. Visibility into actions taken by the
runtime is invaluable in integrating Python into an otherwise secure
and/or monitored environment. |
PEP 552 – Deterministic pycs
Author:
Benjamin Peterson <benjamin at python.org>
Status:
Final
Type:
Standards Track
Created:
04-Sep-2017
Python-Version:
3.7
Post-History:
07-Sep-2017
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Specification
References
Credits
Copyright
Abstract
This PEP ... | Final | PEP 552 – Deterministic pycs | Standards Track | This PEP proposes an extension to the pyc format to make it more deterministic. |
PEP 553 – Built-in breakpoint()
Author:
Barry Warsaw <barry at python.org>
Status:
Final
Type:
Standards Track
Created:
05-Sep-2017
Python-Version:
3.7
Post-History:
05-Sep-2017, 07-Sep-2017, 13-Sep-2017
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Proposal
Environment variable
Implementatio... | Final | PEP 553 – Built-in breakpoint() | Standards Track | This PEP proposes adding a new built-in function called breakpoint() which
enters a Python debugger at the point of the call. Additionally, two new
names are added to the sys module to make the choice of which debugger is
entered configurable. |
PEP 555 – Context-local variables (contextvars)
Author:
Koos Zevenhoven
Status:
Withdrawn
Type:
Standards Track
Created:
06-Sep-2017
Python-Version:
3.7
Post-History:
06-Sep-2017
Table of Contents
Abstract
Rationale
Proposal
Semantics and higher-level API
Core concept
Refactoring into subroutines
Semantics for gen... | Withdrawn | PEP 555 – Context-local variables (contextvars) | Standards Track | Sometimes, in special cases, it is desired that code can pass information down the function call chain to the callees without having to explicitly pass the information as arguments to each function in the call chain. This proposal describes a construct which allows code to explicitly switch in and out of a context wher... |
PEP 556 – Threaded garbage collection
Author:
Antoine Pitrou <solipsis at pitrou.net>
Status:
Deferred
Type:
Standards Track
Created:
08-Sep-2017
Python-Version:
3.7
Post-History:
08-Sep-2017
Table of Contents
Deferral Notice
Abstract
Terminology
Rationale
Proposal
New public APIs
Intended use
Non-goals
Internal... | Deferred | PEP 556 – Threaded garbage collection | Standards Track | This PEP proposes a new optional mode of operation for CPython’s cyclic
garbage collector (GC) where implicit (i.e. opportunistic) collections
happen in a dedicated thread rather than synchronously. |
PEP 557 – Data Classes
Author:
Eric V. Smith <eric at trueblade.com>
Status:
Final
Type:
Standards Track
Created:
02-Jun-2017
Python-Version:
3.7
Post-History:
08-Sep-2017, 25-Nov-2017, 30-Nov-2017, 01-Dec-2017, 02-Dec-2017, 06-Jan-2018, 04-Mar-2018
Resolution:
Python-Dev message
Table of Contents
Notice for Revie... | Final | PEP 557 – Data Classes | Standards Track | 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, you are free to use
inheritance, metaclasses, docstrings, user-defin... |
PEP 559 – Built-in noop()
Author:
Barry Warsaw <barry at python.org>
Status:
Rejected
Type:
Standards Track
Created:
08-Sep-2017
Python-Version:
3.7
Post-History:
09-Sep-2017
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Implementation
Rejected alternatives
noop() returns something
Referenc... | Rejected | PEP 559 – Built-in noop() | Standards Track | This PEP proposes adding a new built-in function called noop() which does
nothing but return None. |
PEP 560 – Core support for typing module and generic types
Author:
Ivan Levkivskyi <levkivskyi at gmail.com>
Status:
Final
Type:
Standards Track
Created:
03-Sep-2017
Python-Version:
3.7
Post-History:
09-Sep-2017, 14-Nov-2017
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Performance
Metaclass ... | Final | PEP 560 – Core support for typing module and generic types | Standards Track | Initially PEP 484 was designed in such way that it would not introduce
any changes to the core CPython interpreter. Now type hints and
the typing module are extensively used by the community, e.g. PEP 526
and PEP 557 extend the usage of type hints, and the backport of typing
on PyPI has 1M downloads/month. Therefore, t... |
PEP 561 – Distributing and Packaging Type Information
Author:
Ethan Smith <ethan at ethanhs.me>
Status:
Final
Type:
Standards Track
Topic:
Packaging, Typing
Created:
09-Sep-2017
Python-Version:
3.7
Post-History:
10-Sep-2017, 12-Sep-2017, 06-Oct-2017, 26-Oct-2017, 12-Apr-2018
Table of Contents
Abstract
Rationale
D... | Final | PEP 561 – Distributing and Packaging Type Information | Standards Track | PEP 484 introduced type hinting to Python, with goals of making typing
gradual and easy to adopt. Currently, typing information must be distributed
manually. This PEP provides a standardized means to leverage existing tooling
to package and distribute type information with minimal work and an ordering
for type checkers... |
PEP 562 – Module __getattr__ and __dir__
Author:
Ivan Levkivskyi <levkivskyi at gmail.com>
Status:
Final
Type:
Standards Track
Created:
09-Sep-2017
Python-Version:
3.7
Post-History:
09-Sep-2017
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Specification
Backwards compatibility and impact on p... | Final | PEP 562 – Module __getattr__ and __dir__ | Standards Track | It is proposed to support __getattr__ and __dir__ function defined
on modules to provide basic customization of module attribute access. |
PEP 564 – Add new time functions with nanosecond resolution
Author:
Victor Stinner <vstinner at python.org>
Status:
Final
Type:
Standards Track
Created:
16-Oct-2017
Python-Version:
3.7
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Float type limited to 104 days
Previous rejected PEP
Issues ca... | Final | PEP 564 – Add new time functions with nanosecond resolution | Standards Track | Add six new “nanosecond” variants of existing functions to the time
module: clock_gettime_ns(), clock_settime_ns(),
monotonic_ns(), perf_counter_ns(), process_time_ns() and
time_ns(). While similar to the existing functions without the
_ns suffix, they provide nanosecond resolution: they return a number of
nanoseconds... |
PEP 565 – Show DeprecationWarning in __main__
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Final
Type:
Standards Track
Created:
12-Nov-2017
Python-Version:
3.7
Post-History:
12-Nov-2017, 25-Nov-2017
Resolution:
Python-Dev message
Table of Contents
Abstract
Specification
New default warnings filter entry
... | Final | PEP 565 – Show DeprecationWarning in __main__ | Standards Track | In Python 2.7 and Python 3.2, the default warning filters were updated to hide
DeprecationWarning by default, such that deprecation warnings in development
tools that were themselves written in Python (e.g. linters, static analysers,
test runners, code generators), as well as any other applications that merely
happened... |
PEP 567 – Context Variables
Author:
Yury Selivanov <yury at edgedb.com>
Status:
Final
Type:
Standards Track
Created:
12-Dec-2017
Python-Version:
3.7
Post-History:
12-Dec-2017, 28-Dec-2017, 16-Jan-2018
Table of Contents
Abstract
API Design and Implementation Revisions
Rationale
Introduction
Specification
contextvar... | Final | PEP 567 – Context Variables | Standards Track | This PEP proposes a new contextvars module and a set of new
CPython C APIs to support context variables. This concept is
similar to thread-local storage (TLS), but, unlike TLS, it also allows
correctly keeping track of values per asynchronous task, e.g.
asyncio.Task. |
PEP 568 – Generator-sensitivity for Context Variables
Author:
Nathaniel J. Smith <njs at pobox.com>
Status:
Deferred
Type:
Standards Track
Created:
04-Jan-2018
Python-Version:
3.8
Post-History:
Table of Contents
Abstract
Rationale
High-level summary
Specification
Review of PEP 567
Changes from PEP 567 to this PEP... | Deferred | PEP 568 – Generator-sensitivity for Context Variables | Standards Track | Context variables provide a generic mechanism for tracking dynamic,
context-local state, similar to thread-local storage but generalized
to cope work with other kinds of thread-like contexts, such as asyncio
Tasks. PEP 550 proposed a mechanism for context-local state that was
also sensitive to generator context, but th... |
PEP 569 – Python 3.8 Release Schedule
Author:
Łukasz Langa <lukasz at python.org>
Status:
Active
Type:
Informational
Topic:
Release
Created:
27-Jan-2018
Python-Version:
3.8
Table of Contents
Abstract
Release Manager and Crew
3.8 Lifespan
Release Schedule
3.8.0 schedule
Bugfix releases
Source-only security fix rele... | Active | PEP 569 – Python 3.8 Release Schedule | Informational | This document describes the development and release schedule for
Python 3.8. The schedule primarily concerns itself with PEP-sized
items. |
PEP 572 – Assignment Expressions
Author:
Chris Angelico <rosuav at gmail.com>, Tim Peters <tim.peters at gmail.com>,
Guido van Rossum <guido at python.org>
Status:
Final
Type:
Standards Track
Created:
28-Feb-2018
Python-Version:
3.8
Post-History:
28-Feb-2018, 02-Mar-2018, 23-Mar-2018, 04-Apr-2018, 17-Apr-2018,
25-Apr... | Final | PEP 572 – Assignment Expressions | Standards Track | This is a proposal for creating a way to assign to variables within an
expression using the notation NAME := expr. |
PEP 575 – Unifying function/method classes
Author:
Jeroen Demeyer <J.Demeyer at UGent.be>
Status:
Withdrawn
Type:
Standards Track
Created:
27-Mar-2018
Python-Version:
3.8
Post-History:
31-Mar-2018, 12-Apr-2018, 27-Apr-2018, 05-May-2018
Table of Contents
Withdrawal notice
Abstract
Motivation
New classes
base_functi... | Withdrawn | PEP 575 – Unifying function/method classes | Standards Track | Reorganize the class hierarchy for functions and methods
with the goal of reducing the difference between
built-in functions (implemented in C) and Python functions.
Mainly, make built-in functions behave more like Python functions
without sacrificing performance. |
PEP 577 – Augmented Assignment Expressions
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Withdrawn
Type:
Standards Track
Created:
14-May-2018
Python-Version:
3.8
Post-History:
22-May-2018
Table of Contents
PEP Withdrawal
Abstract
Syntax and semantics
Augmented assignment expressions
Adding an inline assig... | Withdrawn | PEP 577 – Augmented Assignment Expressions | Standards Track | This is a proposal to allow augmented assignments such as x += 1 to be
used as expressions, not just statements. |
PEP 583 – A Concurrency Memory Model for Python
Author:
Jeffrey Yasskin <jyasskin at google.com>
Status:
Withdrawn
Type:
Informational
Created:
22-Mar-2008
Post-History:
Table of Contents
Abstract
Rationale
A couple definitions
Two simple memory models
Sequential Consistency
Happens-before consistency
An example
... | Withdrawn | PEP 583 – A Concurrency Memory Model for Python | Informational | This PEP describes how Python programs may behave in the presence of
concurrent reads and writes to shared variables from multiple threads.
We use a happens before relation to define when variable accesses
are ordered or concurrent. Nearly all programs should simply use locks
to guard their shared variables, and this ... |
PEP 597 – Add optional EncodingWarning
Author:
Inada Naoki <songofacandy at gmail.com>
Status:
Final
Type:
Standards Track
Created:
05-Jun-2019
Python-Version:
3.10
Table of Contents
Abstract
Motivation
Using the default encoding is a common mistake
Explicit way to use locale-specific encoding
Prepare to change th... | Final | PEP 597 – Add optional EncodingWarning | Standards Track | Add a new warning category EncodingWarning. It is emitted when the
encoding argument to open() is omitted and the default
locale-specific encoding is used. |
PEP 606 – Python Compatibility Version
Author:
Victor Stinner <vstinner at python.org>
Status:
Rejected
Type:
Standards Track
Created:
18-Oct-2019
Python-Version:
3.9
Table of Contents
Abstract
Rationale
The need to evolve frequently
Partial compatibility to minimize the Python maintenance burden
Cases excluded fr... | Rejected | PEP 606 – Python Compatibility Version | Standards Track | Add sys.set_python_compat_version(version) to enable partial
compatibility with requested Python version. Add
sys.get_python_compat_version(). |
PEP 608 – Coordinated Python release
Author:
Miro Hrončok <miro at hroncok.cz>,
Victor Stinner <vstinner at python.org>
Status:
Rejected
Type:
Standards Track
Created:
25-Oct-2019
Python-Version:
3.9
Table of Contents
Abstract
Rationale
Too few projects are involved in the Python beta phase
DeprecationWarning is b... | Rejected | PEP 608 – Coordinated Python release | Standards Track | Block a Python release until a compatible version of selected projects
is available. |
PEP 611 – The one million limit
Author:
Mark Shannon <mark at hotpy.org>
Status:
Withdrawn
Type:
Standards Track
Created:
05-Dec-2019
Post-History:
Table of Contents
Abstract
Motivation
Is this a worthwhile trade off?
Rationale
One million
Specification
Recursion depth
Soft and hard limits
Introspecting and... | Withdrawn | PEP 611 – The one million limit | Standards Track | This PR proposes a soft limit of one million (1 000 000), and a larger hard limit
for various aspects of Python code and its implementation. |
PEP 619 – Python 3.10 Release Schedule
Author:
Pablo Galindo Salgado <pablogsal at python.org>
Status:
Active
Type:
Informational
Topic:
Release
Created:
25-May-2020
Python-Version:
3.10
Table of Contents
Abstract
Release Manager and Crew
Release Schedule
3.10.0 schedule
Bugfix releases
Source-only security fix re... | Active | PEP 619 – Python 3.10 Release Schedule | Informational | This document describes the development and release schedule for
Python 3.10. The schedule primarily concerns itself with PEP-sized
items. |
PEP 620 – Hide implementation details from the C API
Author:
Victor Stinner <vstinner at python.org>
Status:
Withdrawn
Type:
Standards Track
Created:
19-Jun-2020
Python-Version:
3.12
Table of Contents
Abstract
PEP withdrawn
Motivation
The C API blocks CPython evolutions
Same CPython design since 1990: structures a... | Withdrawn | PEP 620 – Hide implementation details from the C API | Standards Track | Introduce C API incompatible changes to hide implementation details. |
PEP 624 – Remove Py_UNICODE encoder APIs
Author:
Inada Naoki <songofacandy at gmail.com>
Status:
Final
Type:
Standards Track
Created:
06-Jul-2020
Python-Version:
3.11
Post-History:
08-Jul-2020
Table of Contents
Abstract
Motivation
Rationale
Deprecated since Python 3.3
Inefficient
Not used widely
Alternative APIs... | Final | PEP 624 – Remove Py_UNICODE encoder APIs | Standards Track | This PEP proposes to remove deprecated Py_UNICODE encoder APIs in Python 3.11: |
PEP 628 – Add math.tau
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Final
Type:
Standards Track
Created:
28-Jun-2011
Python-Version:
3.6
Post-History:
28-Jun-2011
Table of Contents
Abstract
PEP Acceptance
The Rationale for Tau
Other Resources
Copyright
Abstract
In honour of Tau Day 2011, this PEP prop... | Final | PEP 628 – Add math.tau | Standards Track | In honour of Tau Day 2011, this PEP proposes the addition of the circle
constant math.tau to the Python standard library. |
PEP 640 – Unused variable syntax
Author:
Thomas Wouters <thomas at python.org>
Status:
Rejected
Type:
Standards Track
Created:
04-Oct-2020
Python-Version:
3.10
Post-History:
19-Oct-2020
Resolution:
Python-Dev message
Table of Contents
Rejection Note
Abstract
Motivation
Rationale
Specification
Backwards Compatibili... | Rejected | PEP 640 – Unused variable syntax | Standards Track | This PEP proposes new syntax for unused variables, providing a pseudo-name
that can be assigned to but not otherwise used. The assignment doesn’t
actually happen, and the value is discarded instead. |
PEP 651 – Robust Stack Overflow Handling
Author:
Mark Shannon <mark at hotpy.org>
Status:
Rejected
Type:
Standards Track
Created:
18-Jan-2021
Post-History:
19-Jan-2021
Table of Contents
Rejection Notice
Abstract
Motivation
Rationale
Specification
StackOverflow exception
RecursionOverflow exception
Decoupling the P... | Rejected | PEP 651 – Robust Stack Overflow Handling | Standards Track | This PEP proposes that Python should treat machine stack overflow differently from runaway recursion. |
PEP 653 – Precise Semantics for Pattern Matching
Author:
Mark Shannon <mark at hotpy.org>
Status:
Draft
Type:
Standards Track
Created:
09-Feb-2021
Post-History:
18-Feb-2021
Table of Contents
Abstract
Motivation
Precise semantics
Improved control over class matching
Robustness
Efficient implementation
Rationale
S... | Draft | PEP 653 – Precise Semantics for Pattern Matching | Standards Track | This PEP proposes a semantics for pattern matching that respects the general concept of PEP 634,
but is more precise, easier to reason about, and should be faster. |
PEP 659 – Specializing Adaptive Interpreter
Author:
Mark Shannon <mark at hotpy.org>
Status:
Draft
Type:
Informational
Created:
13-Apr-2021
Post-History:
11-May-2021
Table of Contents
Abstract
Motivation
Rationale
Performance
Implementation
Overview
Quickening
Adaptive instructions
Specialization
Ancillary data
... | Draft | PEP 659 – Specializing Adaptive Interpreter | Informational | In order to perform well, virtual machines for dynamic languages must
specialize the code that they execute to the types and values in the
program being run. This specialization is often associated with “JIT”
compilers, but is beneficial even without machine code generation. |
PEP 664 – Python 3.11 Release Schedule
Author:
Pablo Galindo Salgado <pablogsal at python.org>
Status:
Active
Type:
Informational
Topic:
Release
Created:
12-Jul-2021
Python-Version:
3.11
Table of Contents
Abstract
Release Manager and Crew
Release Schedule
3.11.0 schedule
Bugfix releases
3.11 Lifespan
Features fo... | Active | PEP 664 – Python 3.11 Release Schedule | Informational | This document describes the development and release schedule for
Python 3.11. The schedule primarily concerns itself with PEP-sized
items. |
PEP 666 – Reject Foolish Indentation
Author:
Laura Creighton <lac at strakt.com>
Status:
Rejected
Type:
Standards Track
Created:
03-Dec-2001
Python-Version:
2.2
Post-History:
05-Dec-2001
Table of Contents
Abstract
Rationale
References
Copyright
Abstract
Everybody agrees that mixing tabs and spaces is a bad idea... | Rejected | PEP 666 – Reject Foolish Indentation | Standards Track | Everybody agrees that mixing tabs and spaces is a bad idea. Some
people want more than this. I propose that we let people define
whatever Python behaviour they want, so it will only run the way
they like it, and will not run the way they don’t like it. We
will do this with a command line switch. Programs that aren’... |
PEP 667 – Consistent views of namespaces
Author:
Mark Shannon <mark at hotpy.org>
Status:
Draft
Type:
Standards Track
Created:
30-Jul-2021
Python-Version:
3.13
Post-History:
20-Aug-2021
Table of Contents
Abstract
Motivation
Rationale
Specification
Python
C-API
Extensions to the API
Changes to existing APIs
Behav... | Draft | PEP 667 – Consistent views of namespaces | Standards Track | In early versions of Python all namespaces, whether in functions,
classes or modules, were all implemented the same way: as a dictionary. |
PEP 670 – Convert macros to functions in the Python C API
Author:
Erlend Egeberg Aasland <erlend at python.org>,
Victor Stinner <vstinner at python.org>
Status:
Final
Type:
Standards Track
Created:
19-Oct-2021
Python-Version:
3.11
Post-History:
20-Oct-2021,
08-Feb-2022,
22-Feb-2022
Resolution:
Python-Dev thread
Ta... | Final | PEP 670 – Convert macros to functions in the Python C API | Standards Track | Macros in the C API will be converted to static inline functions or
regular functions. This will help avoid macro pitfalls in C/C++, and
make the functions usable from other programming languages. |
PEP 672 – Unicode-related Security Considerations for Python
Author:
Petr Viktorin <encukou at gmail.com>
Status:
Active
Type:
Informational
Created:
01-Nov-2021
Post-History:
01-Nov-2021
Table of Contents
Abstract
Introduction
Acknowledgement
Confusing Features
ASCII-only Considerations
Confusables and Typos
Cont... | Active | PEP 672 – Unicode-related Security Considerations for Python | Informational | This document explains possible ways to misuse Unicode to write Python
programs that appear to do something else than they actually do. |
PEP 674 – Disallow using macros as l-values
Author:
Victor Stinner <vstinner at python.org>
Status:
Deferred
Type:
Standards Track
Created:
30-Nov-2021
Python-Version:
3.12
Table of Contents
Abstract
PEP Deferral
Rationale
Using a macro as a an l-value
CPython nogil fork
HPy project
GraalVM Python
Specification
... | Deferred | PEP 674 – Disallow using macros as l-values | Standards Track | Disallow using macros as l-values. For example,
Py_TYPE(obj) = new_type now fails with a compiler error. |
PEP 693 – Python 3.12 Release Schedule
Author:
Thomas Wouters <thomas at python.org>
Status:
Active
Type:
Informational
Topic:
Release
Created:
24-May-2022
Python-Version:
3.12
Table of Contents
Abstract
Release Manager and Crew
Release Schedule
3.12.0 schedule
Bugfix releases
Source-only security fix releases
3.1... | Active | PEP 693 – Python 3.12 Release Schedule | Informational | This document describes the development and release schedule for
Python 3.12. |
PEP 719 – Python 3.13 Release Schedule
Author:
Thomas Wouters <thomas at python.org>
Status:
Active
Type:
Informational
Topic:
Release
Created:
26-May-2023
Python-Version:
3.13
Table of Contents
Abstract
Release Manager and Crew
Release Schedule
3.13.0 schedule
3.13 Lifespan
Copyright
Abstract
This document d... | Active | PEP 719 – Python 3.13 Release Schedule | Informational | This document describes the development and release schedule for
Python 3.13. |
PEP 733 – An Evaluation of Python’s Public C API
Author:
Erlend Egeberg Aasland <erlend at python.org>,
Domenico Andreoli <domenico.andreoli at linux.com>,
Stefan Behnel <stefan_ml at behnel.de>,
Carl Friedrich Bolz-Tereick <cfbolz at gmx.de>,
Simon Cross <hodgestar at gmail.com>,
Steve Dower <steve.dower at python.o... | Draft | PEP 733 – An Evaluation of Python’s Public C API | Informational | This informational PEP describes our shared view of the public C API. The
document defines: |
PEP 754 – IEEE 754 Floating Point Special Values
Author:
Gregory R. Warnes <gregory_r_warnes at groton.pfizer.com>
Status:
Rejected
Type:
Standards Track
Created:
28-Mar-2003
Python-Version:
2.3
Post-History:
Table of Contents
Rejection Notice
Abstract
Rationale
API Definition
Constants
Functions
Example
Implemen... | Rejected | PEP 754 – IEEE 754 Floating Point Special Values | Standards Track | This PEP proposes an API and a provides a reference module that
generates and tests for IEEE 754 double-precision special values:
positive infinity, negative infinity, and not-a-number (NaN). |
PEP 801 – Reserved
Author:
Barry Warsaw <barry at python.org>
Status:
Active
Type:
Informational
Created:
21-Jun-2018
Table of Contents
Abstract
Copyright
Abstract
This PEP is reserved for future use, because
We are the 801.
Contact the author for details.
Copyright
This document has been placed in the public... | Active | PEP 801 – Reserved | Informational | This PEP is reserved for future use, because
We are the 801.
Contact the author for details. |
PEP 3000 – Python 3000
Author:
Guido van Rossum <guido at python.org>
Status:
Final
Type:
Process
Created:
05-Apr-2006
Post-History:
Table of Contents
Abstract
Naming
PEP Numbering
Timeline
Compatibility and Transition
Implementation Language
Meta-Contributions
References
Copyright
Abstract
This PEP sets guide... | Final | PEP 3000 – Python 3000 | Process | This PEP sets guidelines for Python 3000 development. Ideally, we
first agree on the process, and start discussing features only after
the process has been decided and specified. In practice, we’ll be
discussing features and process simultaneously; often the debate about
a particular feature will prompt a process dis... |
PEP 3001 – Procedure for reviewing and improving standard library modules
Author:
Georg Brandl <georg at python.org>
Status:
Withdrawn
Type:
Process
Created:
05-Apr-2006
Post-History:
Table of Contents
Abstract
Removal of obsolete modules
Renaming modules
Code cleanup
Enhancement of test and documentation coverag... | Withdrawn | PEP 3001 – Procedure for reviewing and improving standard library modules | Process | This PEP describes a procedure for reviewing and improving standard
library modules, especially those written in Python, making them ready
for Python 3000. There can be different steps of refurbishing, each
of which is described in a section below. Of course, not every step
has to be performed for every module. |
PEP 3002 – Procedure for Backwards-Incompatible Changes
Author:
Steven Bethard <steven.bethard at gmail.com>
Status:
Final
Type:
Process
Created:
27-Mar-2006
Post-History:
27-Mar-2006, 13-Apr-2006
Table of Contents
Abstract
Rationale
Python Enhancement Proposals
Identifying Problematic Code
References
Copyright
... | Final | PEP 3002 – Procedure for Backwards-Incompatible Changes | Process | This PEP describes the procedure for changes to Python that are
backwards-incompatible between the Python 2.X series and Python 3000.
All such changes must be documented by an appropriate Python 3000 PEP
and must be accompanied by code that can identify when pieces of
Python 2.X code may be problematic in Python 3000. |
PEP 3003 – Python Language Moratorium
Author:
Brett Cannon, Jesse Noller, Guido van Rossum
Status:
Final
Type:
Process
Created:
21-Oct-2009
Post-History:
03-Nov-2009
Table of Contents
Abstract
Rationale
Details
Cannot Change
Case-by-Case Exemptions
Allowed to Change
Retroactive
Extensions
Copyright
References
... | Final | PEP 3003 – Python Language Moratorium | Process | This PEP proposes a temporary moratorium (suspension) of all changes
to the Python language syntax, semantics, and built-ins for a period
of at least two years from the release of Python 3.1. In particular, the
moratorium would include Python 3.2 (to be released 18-24 months after
3.1) but allow Python 3.3 (assuming i... |
PEP 3099 – Things that will Not Change in Python 3000
Author:
Georg Brandl <georg at python.org>
Status:
Final
Type:
Process
Created:
04-Apr-2006
Post-History:
Table of Contents
Abstract
Core language
Builtins
Standard types
Coding style
Interactive Interpreter
Copyright
Abstract
Some ideas are just bad. Whil... | Final | PEP 3099 – Things that will Not Change in Python 3000 | Process | Some ideas are just bad. While some thoughts on Python evolution are
constructive, some go against the basic tenets of Python so
egregiously that it would be like asking someone to run in a circle:
it gets you nowhere, even for Python 3000, where extraordinary
proposals are allowed. This PEP tries to list all BDFL pr... |
PEP 3100 – Miscellaneous Python 3.0 Plans
Author:
Brett Cannon <brett at python.org>
Status:
Final
Type:
Process
Created:
20-Aug-2004
Post-History:
Table of Contents
Abstract
General goals
Influencing PEPs
Style changes
Core language
Atomic Types
Built-in Namespace
Standard library
Outstanding Issues
References
C... | Final | PEP 3100 – Miscellaneous Python 3.0 Plans | Process | This PEP, previously known as PEP 3000, describes smaller scale changes
and new features for which no separate PEP is written yet, all targeted
for Python 3000. |
PEP 3101 – Advanced String Formatting
Author:
Talin <viridia at gmail.com>
Status:
Final
Type:
Standards Track
Created:
16-Apr-2006
Python-Version:
3.0
Post-History:
28-Apr-2006, 06-May-2006, 10-Jun-2007, 14-Aug-2007, 14-Sep-2008
Table of Contents
Abstract
Rationale
Specification
String Methods
Format Strings
Simp... | Final | PEP 3101 – Advanced String Formatting | Standards Track | This PEP proposes a new system for built-in string formatting
operations, intended as a replacement for the existing ‘%’ string
formatting operator. |
PEP 3102 – Keyword-Only Arguments
Author:
Talin <viridia at gmail.com>
Status:
Final
Type:
Standards Track
Created:
22-Apr-2006
Python-Version:
3.0
Post-History:
28-Apr-2006, 19-May-2006
Table of Contents
Abstract
Rationale
Specification
Function Calling Behavior
Backwards Compatibility
Copyright
Abstract
This ... | Final | PEP 3102 – Keyword-Only Arguments | Standards Track | This PEP proposes a change to the way that function arguments are
assigned to named parameter slots. In particular, it enables the
declaration of “keyword-only” arguments: arguments that can only
be supplied by keyword and which will never be automatically
filled in by a positional argument. |
PEP 3103 – A Switch/Case Statement
Author:
Guido van Rossum <guido at python.org>
Status:
Rejected
Type:
Standards Track
Created:
25-Jun-2006
Python-Version:
3.0
Post-History:
26-Jun-2006
Table of Contents
Rejection Notice
Abstract
Rationale
Basic Syntax
Alternative 1
Alternative 2
Alternative 3
Alternative 4
Ex... | Rejected | PEP 3103 – A Switch/Case Statement | Standards Track | Python-dev has recently seen a flurry of discussion on adding a switch
statement. In this PEP I’m trying to extract my own preferences from
the smorgasbord of proposals, discussing alternatives and explaining
my choices where I can. I’ll also indicate how strongly I feel about
alternatives I discuss. |
PEP 3104 – Access to Names in Outer Scopes
Author:
Ka-Ping Yee <ping at zesty.ca>
Status:
Final
Type:
Standards Track
Created:
12-Oct-2006
Python-Version:
3.0
Post-History:
Table of Contents
Abstract
Rationale
Other Languages
JavaScript, Perl, Scheme, Smalltalk, GNU C, C# 2.0
Ruby (as of 1.8)
Overview of Propos... | Final | PEP 3104 – Access to Names in Outer Scopes | Standards Track | 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 (by
simple assignment) or the module-global scope (using a global
... |
PEP 3105 – Make print a function
Author:
Georg Brandl <georg at python.org>
Status:
Final
Type:
Standards Track
Created:
19-Nov-2006
Python-Version:
3.0
Post-History:
Table of Contents
Abstract
Rationale
Specification
Backwards Compatibility
Implementation
References
Copyright
Abstract
The title says it all – ... | Final | PEP 3105 – Make print a function | Standards Track | The title says it all – this PEP proposes a new print() builtin
that replaces the print statement and suggests a specific signature
for the new function. |
PEP 3106 – Revamping dict.keys(), .values() and .items()
Author:
Guido van Rossum
Status:
Final
Type:
Standards Track
Created:
19-Dec-2006
Python-Version:
3.0
Post-History:
Table of Contents
Abstract
Introduction
Specification
Open Issues
References
Abstract
This PEP proposes to change the .keys(), .values() a... | Final | PEP 3106 – Revamping dict.keys(), .values() and .items() | Standards Track | This PEP proposes to change the .keys(), .values() and .items()
methods of the built-in dict type to return a set-like or unordered
container object whose contents are derived from the underlying
dictionary rather than a list which is a copy of the keys, etc.; and
to remove the .iterkeys(), .itervalues() and .iteritems... |
PEP 3107 – Function Annotations
Author:
Collin Winter <collinwinter at google.com>,
Tony Lownds <tony at lownds.com>
Status:
Final
Type:
Standards Track
Created:
02-Dec-2006
Python-Version:
3.0
Post-History:
Table of Contents
Abstract
Rationale
Fundamentals of Function Annotations
Syntax
Parameters
Return Values
... | Final | PEP 3107 – Function Annotations | Standards Track | This PEP introduces a syntax for adding arbitrary metadata annotations
to Python functions [1]. |
PEP 3108 – Standard Library Reorganization
Author:
Brett Cannon <brett at python.org>
Status:
Final
Type:
Standards Track
Created:
01-Jan-2007
Python-Version:
3.0
Post-History:
28-Apr-2008
Table of Contents
Abstract
Modules to Remove
Previously deprecated [done]
Platform-specific with minimal use [done]
IRIX
Mac-s... | Final | PEP 3108 – Standard Library Reorganization | Standards Track | Just like the language itself, Python’s standard library (stdlib) has
grown over the years to be very rich. But over time some modules
have lost their need to be included with Python. There has also been
an introduction of a naming convention for modules since Python’s
inception that not all modules follow. |
PEP 3109 – Raising Exceptions in Python 3000
Author:
Collin Winter <collinwinter at google.com>
Status:
Final
Type:
Standards Track
Created:
19-Jan-2006
Python-Version:
3.0
Post-History:
Table of Contents
Abstract
Rationale
Grammar Changes
Changes to Builtin Types
Semantic Changes
Compatibility Issues
Implementat... | Final | PEP 3109 – Raising Exceptions in Python 3000 | Standards Track | This PEP introduces changes to Python’s mechanisms for raising
exceptions intended to reduce both line noise and the size of the
language. |
PEP 3110 – Catching Exceptions in Python 3000
Author:
Collin Winter <collinwinter at google.com>
Status:
Final
Type:
Standards Track
Created:
16-Jan-2006
Python-Version:
3.0
Post-History:
Table of Contents
Abstract
Rationale
Grammar Changes
Semantic Changes
Compatibility Issues
2.6 - 3.0 Compatibility
Open Issu... | Final | PEP 3110 – Catching Exceptions in Python 3000 | Standards Track | This PEP introduces changes intended to help eliminate ambiguities
in Python’s grammar, simplify exception classes, simplify garbage
collection for exceptions and reduce the size of the language in
Python 3.0. |
PEP 3111 – Simple input built-in in Python 3000
Author:
Andre Roberge <andre.roberge at gmail.com>
Status:
Final
Type:
Standards Track
Created:
13-Sep-2006
Python-Version:
3.0
Post-History:
22-Dec-2006
Table of Contents
Abstract
Motivation
Rationale
Specification
Naming Discussion
References
Copyright
Abstract
... | Final | PEP 3111 – Simple input built-in in Python 3000 | Standards Track | Input and output are core features of computer programs. Currently,
Python provides a simple means of output through the print keyword
and two simple means of interactive input through the input()
and raw_input() built-in functions. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.