text stringlengths 330 67k | status stringclasses 9
values | title stringlengths 18 80 | type stringclasses 3
values | abstract stringlengths 4 917 |
|---|---|---|---|---|
PEP 328 – Imports: Multi-Line and Absolute/Relative
Author:
Aahz <aahz at pythoncraft.com>
Status:
Final
Type:
Standards Track
Created:
21-Dec-2003
Python-Version:
2.4, 2.5, 2.6
Post-History:
08-Mar-2004
Table of Contents
Abstract
Timeline
Rationale for Parentheses
Rationale for Absolute Imports
Rationale for Rela... | Final | PEP 328 – Imports: Multi-Line and Absolute/Relative | Standards Track | The import statement has two problems: |
PEP 329 – Treating Builtins as Constants in the Standard Library
Author:
Raymond Hettinger <python at rcn.com>
Status:
Rejected
Type:
Standards Track
Created:
18-Apr-2004
Python-Version:
2.4
Post-History:
18-Apr-2004
Table of Contents
Abstract
Status
Motivation
Proposal
Questions and Answers
Sample Implementation
... | Rejected | PEP 329 – Treating Builtins as Constants in the Standard Library | Standards Track | The proposal is to add a function for treating builtin references as
constants and to apply that function throughout the standard library. |
PEP 330 – Python Bytecode Verification
Author:
Michel Pelletier <michel at users.sourceforge.net>
Status:
Rejected
Type:
Standards Track
Created:
17-Jun-2004
Python-Version:
2.6
Post-History:
Table of Contents
Abstract
Pronouncement
Motivation
Static Constraints on Bytecode Instructions
Static Constraints on Byte... | Rejected | PEP 330 – Python Bytecode Verification | Standards Track | If Python Virtual Machine (PVM) bytecode is not “well-formed” it
is possible to crash or exploit the PVM by causing various errors
such as under/overflowing the value stack or reading/writing into
arbitrary areas of the PVM program space. Most of these kinds of
errors can be eliminated by verifying that PVM bytecode d... |
PEP 331 – Locale-Independent Float/String Conversions
Author:
Christian R. Reis <kiko at async.com.br>
Status:
Final
Type:
Standards Track
Created:
19-Jul-2003
Python-Version:
2.4
Post-History:
21-Jul-2003, 13-Aug-2003, 18-Jun-2004
Table of Contents
Abstract
Introduction
Rationale
Example Problem
Proposal
Potentia... | Final | PEP 331 – Locale-Independent Float/String Conversions | Standards Track | Support for the LC_NUMERIC locale category in Python 2.3 is
implemented only in Python-space. This causes inconsistent
behavior and thread-safety issues for applications that use
extension modules and libraries implemented in C that parse and
generate floats from strings. This document proposes a plan for
removing th... |
PEP 332 – Byte vectors and String/Unicode Unification
Author:
Skip Montanaro <skip at pobox.com>
Status:
Rejected
Type:
Standards Track
Created:
11-Aug-2004
Python-Version:
2.5
Post-History:
Table of Contents
Abstract
Rejection Notice
Rationale
Proposed Implementation
Bytes Object API
Issues
Copyright
Abstract... | Rejected | PEP 332 – Byte vectors and String/Unicode Unification | Standards Track | This PEP outlines the introduction of a raw bytes sequence object
and the unification of the current str and unicode objects. |
PEP 334 – Simple Coroutines via SuspendIteration
Author:
Clark C. Evans <cce at clarkevans.com>
Status:
Withdrawn
Type:
Standards Track
Created:
26-Aug-2004
Python-Version:
3.0
Post-History:
Table of Contents
Abstract
Rationale
Semantics
Simple Iterators
Introducing SuspendIteration
Application Iterators
Complica... | Withdrawn | PEP 334 – Simple Coroutines via SuspendIteration | Standards Track | Asynchronous application frameworks such as Twisted [1] and Peak
[2], are based on a cooperative multitasking via event queues or
deferred execution. While this approach to application development
does not involve threads and thus avoids a whole class of problems
[3], it creates a different sort of programming challen... |
PEP 335 – Overloadable Boolean Operators
Author:
Gregory Ewing <greg.ewing at canterbury.ac.nz>
Status:
Rejected
Type:
Standards Track
Created:
29-Aug-2004
Python-Version:
3.3
Post-History:
05-Sep-2004, 30-Sep-2011, 25-Oct-2011
Table of Contents
Rejection Notice
Abstract
Background
Motivation
Rationale
Specificati... | Rejected | PEP 335 – Overloadable Boolean Operators | Standards Track | This PEP proposes an extension to permit objects to define their own
meanings for the boolean operators ‘and’, ‘or’ and ‘not’, and suggests
an efficient strategy for implementation. A prototype of this
implementation is available for download. |
PEP 336 – Make None Callable
Author:
Andrew McClelland <eternalsquire at comcast.net>
Status:
Rejected
Type:
Standards Track
Created:
28-Oct-2004
Post-History:
Table of Contents
Abstract
BDFL Pronouncement
Motivation
Rationale
How To Use
References
Copyright
Abstract
None should be a callable object that when ... | Rejected | PEP 336 – Make None Callable | Standards Track | None should be a callable object that when called with any
arguments has no side effect and returns None. |
PEP 337 – Logging Usage in the Standard Library
Author:
Michael P. Dubner <dubnerm at mindless.com>
Status:
Deferred
Type:
Standards Track
Created:
02-Oct-2004
Python-Version:
2.5
Post-History:
10-Nov-2004
Table of Contents
Abstract
PEP Deferral
Rationale
Proposal
Module List
Doubtful Modules
Guidelines for Loggin... | Deferred | PEP 337 – Logging Usage in the Standard Library | Standards Track | This PEP defines a standard for using the logging system (PEP 282) in the
standard library. |
PEP 338 – Executing modules as scripts
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Final
Type:
Standards Track
Created:
16-Oct-2004
Python-Version:
2.5
Post-History:
08-Nov-2004, 11-Feb-2006, 12-Feb-2006, 18-Feb-2006
Table of Contents
Abstract
Rationale
Scope of this proposal
Current Behaviour
Proposed ... | Final | PEP 338 – Executing modules as scripts | Standards Track | This PEP defines semantics for executing any Python module as a
script, either with the -m command line switch, or by invoking
it via runpy.run_module(modulename). |
PEP 339 – Design of the CPython Compiler
Author:
Brett Cannon <brett at python.org>
Status:
Withdrawn
Type:
Informational
Created:
02-Feb-2005
Post-History:
Table of Contents
Abstract
Parse Trees
Abstract Syntax Trees (AST)
Memory Management
Parse Tree to AST
Control Flow Graphs
AST to CFG to Bytecode
Introducing... | Withdrawn | PEP 339 – Design of the CPython Compiler | Informational | Historically (through 2.4), compilation from source code to bytecode
involved two steps: |
PEP 341 – Unifying try-except and try-finally
Author:
Georg Brandl <georg at python.org>
Status:
Final
Type:
Standards Track
Created:
04-May-2005
Python-Version:
2.5
Post-History:
Table of Contents
Abstract
Rationale/Proposal
Changes to the grammar
Implementation
References
Copyright
Abstract
This PEP proposes... | Final | PEP 341 – Unifying try-except and try-finally | Standards Track | This PEP proposes a change in the syntax and semantics of try
statements to allow combined try-except-finally blocks. This
means in short that it would be valid to write: |
PEP 343 – The “with” Statement
Author:
Guido van Rossum, Alyssa Coghlan
Status:
Final
Type:
Standards Track
Created:
13-May-2005
Python-Version:
2.5
Post-History:
02-Jun-2005, 16-Oct-2005, 29-Oct-2005, 23-Apr-2006, 01-May-2006,
30-Jul-2006
Table of Contents
Abstract
Author’s Note
Introduction
Motivation and Summar... | Final | PEP 343 – The “with” Statement | Standards Track | This PEP adds a new statement “with” to the Python language to make
it possible to factor out standard uses of try/finally statements. |
PEP 344 – Exception Chaining and Embedded Tracebacks
Author:
Ka-Ping Yee
Status:
Superseded
Type:
Standards Track
Created:
12-May-2005
Python-Version:
2.5
Post-History:
Table of Contents
Numbering Note
Abstract
Motivation
History
Rationale
Implicit Exception Chaining
Explicit Exception Chaining
Traceback Attribut... | Superseded | PEP 344 – Exception Chaining and Embedded Tracebacks | Standards Track | This PEP proposes three standard attributes on exception instances: the
__context__ attribute for implicitly chained exceptions, the
__cause__ attribute for explicitly chained exceptions, and the
__traceback__ attribute for the traceback. A new raise ... from
statement sets the __cause__ attribute. |
PEP 346 – User Defined (”with”) Statements
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Withdrawn
Type:
Standards Track
Created:
06-May-2005
Python-Version:
2.5
Post-History:
Table of Contents
Abstract
Author’s Note
Introduction
Relationship with other PEPs
User defined statements
Usage syntax for user ... | Withdrawn | PEP 346 – User Defined (”with”) Statements | Standards Track | This PEP is a combination of PEP 310’s “Reliable Acquisition/Release
Pairs” with the “Anonymous Block Statements” of Guido’s PEP 340. This
PEP aims to take the good parts of PEP 340, blend them with parts of
PEP 310 and rearrange the lot into an elegant whole. It borrows from
various other PEPs in order to paint a co... |
PEP 348 – Exception Reorganization for Python 3.0
Author:
Brett Cannon <brett at python.org>
Status:
Rejected
Type:
Standards Track
Created:
28-Jul-2005
Post-History:
Table of Contents
Abstract
Rationale For Wanting Change
Philosophy of Reorganization
New Hierarchy
Differences Compared to Python 2.4
BaseException... | Rejected | PEP 348 – Exception Reorganization for Python 3.0 | Standards Track | Python, as of version 2.4, has 38 exceptions (including warnings) in
the built-in namespace in a rather shallow hierarchy. These
classes have come about over the years without a chance to learn from
experience. This PEP proposes doing a reorganization of the hierarchy
for Python 3.0 when backwards-compatibility is no... |
PEP 349 – Allow str() to return unicode strings
Author:
Neil Schemenauer <nas at arctrix.com>
Status:
Rejected
Type:
Standards Track
Created:
02-Aug-2005
Python-Version:
2.5
Post-History:
06-Aug-2005
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Specification
Backwards Compatibility
Alternati... | Rejected | PEP 349 – Allow str() to return unicode strings | Standards Track | This PEP proposes to change the str() built-in function so that it
can return unicode strings. This change would make it easier to
write code that works with either string type and would also make
some existing code handle unicode strings. The C function
PyObject_Str() would remain unchanged and the function
PyString... |
PEP 350 – Codetags
Author:
Micah Elliott <mde at tracos.org>
Status:
Rejected
Type:
Informational
Created:
27-Jun-2005
Post-History:
10-Aug-2005, 26-Sep-2005
Table of Contents
Rejection Notice
Abstract
What Are Codetags?
Philosophy
Motivation
Examples
Specification
General Syntax
Mnemonics
Fields
DONE File
Tools... | Rejected | PEP 350 – Codetags | Informational | This informational PEP aims to provide guidelines for consistent use
of codetags, which would enable the construction of standard
utilities to take advantage of the codetag information, as well as
making Python code more uniform across projects. Codetags also
represent a very lightweight programming micro-paradigm and... |
PEP 351 – The freeze protocol
Author:
Barry Warsaw <barry at python.org>
Status:
Rejected
Type:
Standards Track
Created:
14-Apr-2005
Post-History:
Table of Contents
Abstract
Rejection Notice
Rationale
Proposal
Sample implementations
Reference implementation
Open issues
Copyright
Abstract
This PEP describes a s... | Rejected | PEP 351 – The freeze protocol | Standards Track | This PEP describes a simple protocol for requesting a frozen,
immutable copy of a mutable object. It also defines a new built-in
function which uses this protocol to provide an immutable copy on any
cooperating object. |
PEP 352 – Required Superclass for Exceptions
Author:
Brett Cannon, Guido van Rossum
Status:
Final
Type:
Standards Track
Created:
27-Oct-2005
Python-Version:
2.5
Post-History:
Table of Contents
Abstract
Requiring a Common Superclass
Exception Hierarchy Changes
Transition Plan
Retracted Ideas
References
Copyright
... | Final | PEP 352 – Required Superclass for Exceptions | Standards Track | In Python 2.4 and before, any (classic) class can be raised as an
exception. The plan for 2.5 was to allow new-style classes, but this
makes the problem worse – it would mean any class (or
instance) can be raised! This is a problem as it prevents any
guarantees from being made about the interface of exceptions.
This P... |
PEP 353 – Using ssize_t as the index type
Author:
Martin von Löwis <martin at v.loewis.de>
Status:
Final
Type:
Standards Track
Created:
18-Dec-2005
Python-Version:
2.5
Post-History:
Table of Contents
Abstract
Rationale
Specification
Conversion guidelines
Discussion
Why not size_t
Why not Py_intptr_t
Doesn’t this ... | Final | PEP 353 – Using ssize_t as the index type | Standards Track | In Python 2.4, indices of sequences are restricted to the C type
int. On 64-bit machines, sequences therefore cannot use the full
address space, and are restricted to 2**31 elements. This PEP proposes
to change this, introducing a platform-specific index type
Py_ssize_t. An implementation of the proposed change is in
h... |
PEP 354 – Enumerations in Python
Author:
Ben Finney <ben+python at benfinney.id.au>
Status:
Superseded
Type:
Standards Track
Created:
20-Dec-2005
Python-Version:
2.6
Post-History:
20-Dec-2005
Superseded-By:
435
Table of Contents
Rejection Notice
Abstract
Motivation
Specification
Rationale – Other designs considere... | Superseded | PEP 354 – Enumerations in Python | Standards Track | This PEP specifies an enumeration data type for Python. |
PEP 355 – Path - Object oriented filesystem paths
Author:
Björn Lindqvist <bjourne at gmail.com>
Status:
Rejected
Type:
Standards Track
Created:
24-Jan-2006
Python-Version:
2.5
Post-History:
Table of Contents
Rejection Notice
Abstract
Background
Motivation
Rationale
Specification
Replacing older functions with th... | Rejected | PEP 355 – Path - Object oriented filesystem paths | Standards Track | This PEP describes a new class, Path, to be added to the os
module, for handling paths in an object oriented fashion. The
“weak” deprecation of various related functions is also discussed
and recommended. |
PEP 356 – Python 2.5 Release Schedule
Author:
Neal Norwitz, Guido van Rossum, Anthony Baxter
Status:
Final
Type:
Informational
Topic:
Release
Created:
07-Feb-2006
Python-Version:
2.5
Post-History:
Table of Contents
Abstract
Release Manager
Release Schedule
Completed features for 2.5
Possible features for 2.5
Defe... | Final | PEP 356 – Python 2.5 Release Schedule | Informational | This document describes the development and release schedule for
Python 2.5. The schedule primarily concerns itself with PEP-sized
items. Small features may be added up to and including the first
beta release. Bugs may be fixed until the final release. |
PEP 357 – Allowing Any Object to be Used for Slicing
Author:
Travis Oliphant <oliphant at ee.byu.edu>
Status:
Final
Type:
Standards Track
Created:
09-Feb-2006
Python-Version:
2.5
Post-History:
Table of Contents
Abstract
Rationale
Proposal
Specification
Implementation Plan
Discussion Questions
Speed
Why not use nb... | Final | PEP 357 – Allowing Any Object to be Used for Slicing | Standards Track | This PEP proposes adding an nb_index slot in PyNumberMethods and an
__index__ special method so that arbitrary objects can be used
whenever integers are explicitly needed in Python, such as in slice
syntax (from which the slot gets its name). |
PEP 358 – The “bytes” Object
Author:
Neil Schemenauer <nas at arctrix.com>, Guido van Rossum <guido at python.org>
Status:
Final
Type:
Standards Track
Created:
15-Feb-2006
Python-Version:
2.6, 3.0
Post-History:
Table of Contents
Update
Abstract
Motivation
Specification
Out of Scope Issues
Open Issues
Frequently A... | Final | PEP 358 – The “bytes” Object | Standards Track | This PEP outlines the introduction of a raw bytes sequence type.
Adding the bytes type is one step in the transition to
Unicode-based str objects which will be introduced in Python 3.0. |
PEP 359 – The “make” Statement
Author:
Steven Bethard <steven.bethard at gmail.com>
Status:
Withdrawn
Type:
Standards Track
Created:
05-Apr-2006
Python-Version:
2.6
Post-History:
05-Apr-2006, 06-Apr-2006, 13-Apr-2006
Table of Contents
Abstract
Withdrawal Notice
Motivation
Example: simple namespaces
Example: GUI ob... | Withdrawn | PEP 359 – The “make” Statement | Standards Track | This PEP proposes a generalization of the class-declaration syntax,
the make statement. The proposed syntax and semantics parallel
the syntax for class definition, and so: |
PEP 360 – Externally Maintained Packages
Author:
Brett Cannon <brett at python.org>
Status:
Final
Type:
Process
Created:
30-May-2006
Post-History:
Table of Contents
Abstract
Externally Maintained Packages
ElementTree
Expat XML parser
Optik
wsgiref
References
Copyright
Warning
No new modules are to be added t... | Final | PEP 360 – Externally Maintained Packages | Process | There are many great pieces of Python software developed outside of
the Python standard library (a.k.a., the “stdlib”). Sometimes it
makes sense to incorporate these externally maintained packages into
the stdlib in order to fill a gap in the tools provided by Python. |
PEP 361 – Python 2.6 and 3.0 Release Schedule
Author:
Neal Norwitz, Barry Warsaw
Status:
Final
Type:
Informational
Topic:
Release
Created:
29-Jun-2006
Python-Version:
2.6, 3.0
Post-History:
17-Mar-2008
Table of Contents
Abstract
Release Manager and Crew
Release Lifespan
Release Schedule
Completed features for 3.0
... | Final | PEP 361 – Python 2.6 and 3.0 Release Schedule | Informational | This document describes the development and release schedule for
Python 2.6 and 3.0. The schedule primarily concerns itself with
PEP-sized items. Small features may be added up to and including
the first beta release. Bugs may be fixed until the final
release. |
PEP 362 – Function Signature Object
Author:
Brett Cannon <brett at python.org>, Jiwon Seo <seojiwon at gmail.com>,
Yury Selivanov <yury at edgedb.com>, Larry Hastings <larry at hastings.org>
Status:
Final
Type:
Standards Track
Created:
21-Aug-2006
Python-Version:
3.3
Post-History:
04-Jun-2012
Resolution:
Python-Dev m... | Final | PEP 362 – Function Signature Object | Standards Track | Python has always supported powerful introspection capabilities,
including introspecting functions and methods (for the rest of
this PEP, “function” refers to both functions and methods). By
examining a function object you can fully reconstruct the function’s
signature. Unfortunately this information is stored in an ... |
PEP 363 – Syntax For Dynamic Attribute Access
Author:
Ben North <ben at redfrontdoor.org>
Status:
Rejected
Type:
Standards Track
Created:
29-Jan-2007
Post-History:
12-Feb-2007
Table of Contents
Abstract
Rationale
Impact On Existing Code
Performance Impact
Error Cases
Draft Implementation
Mailing Lists Discussion
R... | Rejected | PEP 363 – Syntax For Dynamic Attribute Access | Standards Track | Dynamic attribute access is currently possible using the “getattr”
and “setattr” builtins. The present PEP suggests a new syntax to
make such access easier, allowing the coder for example to write: |
PEP 364 – Transitioning to the Py3K Standard Library
Author:
Barry Warsaw <barry at python.org>
Status:
Withdrawn
Type:
Standards Track
Created:
01-Mar-2007
Python-Version:
2.6
Post-History:
Table of Contents
Abstract
Rationale
Supported Renamings
.mv files
Implementation Specification
Programmatic Interface
Open... | Withdrawn | PEP 364 – Transitioning to the Py3K Standard Library | Standards Track | PEP 3108 describes the reorganization of the Python standard library
for the Python 3.0 release. This PEP describes a
mechanism for transitioning from the Python 2.x standard library to
the Python 3.0 standard library. This transition will allow and
encourage Python programmers to use the new Python 3.0 library names... |
PEP 365 – Adding the pkg_resources module
Author:
Phillip J. Eby <pje at telecommunity.com>
Status:
Rejected
Type:
Standards Track
Topic:
Packaging
Created:
30-Apr-2007
Post-History:
30-Apr-2007
Table of Contents
Abstract
Proposal
Rationale
Implementation and Documentation
Copyright
Abstract
This PEP proposes a... | Rejected | PEP 365 – Adding the pkg_resources module | Standards Track | This PEP proposes adding an enhanced version of the pkg_resources
module to the standard library. |
PEP 366 – Main module explicit relative imports
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Final
Type:
Standards Track
Created:
01-May-2007
Python-Version:
2.6, 3.0
Post-History:
01-May-2007, 04-Jul-2007, 07-Jul-2007, 23-Nov-2007
Table of Contents
Abstract
Proposed Change
Rationale for Change
Reference... | Final | PEP 366 – Main module explicit relative imports | Standards Track | This PEP proposes a backwards compatible mechanism that permits
the use of explicit relative imports from executable modules within
packages. Such imports currently fail due to an awkward interaction
between PEP 328 and PEP 338. |
PEP 367 – New Super
Author:
Calvin Spealman <ironfroggy at gmail.com>,
Tim Delaney <timothy.c.delaney at gmail.com>
Status:
Superseded
Type:
Standards Track
Created:
28-Apr-2007
Python-Version:
2.6
Post-History:
28-Apr-2007,
29-Apr-2007,
29-Apr-2007,
14-May-2007
Table of Contents
Numbering Note
Abstract
Rationale
... | Superseded | PEP 367 – New Super | Standards Track | This PEP proposes syntactic sugar for use of the super type to automatically
construct instances of the super type binding to the class that a method was
defined in, and the instance (or class object for classmethods) that the method
is currently acting upon. |
PEP 368 – Standard image protocol and class
Author:
Lino Mastrodomenico <l.mastrodomenico at gmail.com>
Status:
Deferred
Type:
Standards Track
Created:
28-Jun-2007
Python-Version:
2.6, 3.0
Post-History:
Table of Contents
Abstract
PEP Deferral
Rationale
Specification
Python API
Mode Objects
Image Protocol
Image an... | Deferred | PEP 368 – Standard image protocol and class | Standards Track | The current situation of image storage and manipulation in the Python
world is extremely fragmented: almost every library that uses image
objects has implemented its own image class, incompatible with
everyone else’s and often not very pythonic. A basic RGB image class
exists in the standard library (Tkinter.PhotoImag... |
PEP 369 – Post import hooks
Author:
Christian Heimes <christian at python.org>
Status:
Withdrawn
Type:
Standards Track
Created:
02-Jan-2008
Python-Version:
2.6, 3.0
Post-History:
02-Dec-2012
Table of Contents
Withdrawal Notice
Abstract
Rationale
Use cases
Existing implementations
Post import hook implementation
St... | Withdrawn | PEP 369 – Post import hooks | Standards Track | This PEP proposes enhancements for the import machinery to add
post import hooks. It is intended primarily to support the wider
use of abstract base classes that is expected in Python 3.0. |
PEP 370 – Per user site-packages directory
Author:
Christian Heimes <christian at python.org>
Status:
Final
Type:
Standards Track
Created:
11-Jan-2008
Python-Version:
2.6, 3.0
Post-History:
Table of Contents
Abstract
Rationale
Specification
Windows Notes
Unix Notes
Mac OS X Notes
Implementation
Backwards Compat... | Final | PEP 370 – Per user site-packages directory | Standards Track | This PEP proposes a new a per user site-packages directory to allow
users the local installation of Python packages in their home directory. |
PEP 371 – Addition of the multiprocessing package to the standard library
Author:
Jesse Noller <jnoller at gmail.com>,
Richard Oudkerk <r.m.oudkerk at googlemail.com>
Status:
Final
Type:
Standards Track
Created:
06-May-2008
Python-Version:
2.6, 3.0
Post-History:
03-Jun-2008
Table of Contents
Abstract
Rationale
The... | Final | PEP 371 – Addition of the multiprocessing package to the standard library | Standards Track | This PEP proposes the inclusion of the pyProcessing [1] package
into the Python standard library, renamed to “multiprocessing”. |
PEP 372 – Adding an ordered dictionary to collections
Author:
Armin Ronacher <armin.ronacher at active-4.com>,
Raymond Hettinger <python at rcn.com>
Status:
Final
Type:
Standards Track
Created:
15-Jun-2008
Python-Version:
2.7, 3.1
Post-History:
Table of Contents
Abstract
Patch
Rationale
Ordered Dict API
Questions... | Final | PEP 372 – Adding an ordered dictionary to collections | Standards Track | This PEP proposes an ordered dictionary as a new data structure for
the collections module, called “OrderedDict” in this PEP. The
proposed API incorporates the experiences gained from working with
similar implementations that exist in various real-world applications
and other programming languages. |
PEP 373 – Python 2.7 Release Schedule
Author:
Benjamin Peterson <benjamin at python.org>
Status:
Final
Type:
Informational
Topic:
Release
Created:
03-Nov-2008
Python-Version:
2.7
Table of Contents
Abstract
Update (April 2014)
Release Manager and Crew
Maintenance releases
2.7.0 Release Schedule
Possible features fo... | Final | PEP 373 – Python 2.7 Release Schedule | Informational | This document describes the development and release schedule for
Python 2.7. |
PEP 375 – Python 3.1 Release Schedule
Author:
Benjamin Peterson <benjamin at python.org>
Status:
Final
Type:
Informational
Topic:
Release
Created:
08-Feb-2009
Python-Version:
3.1
Table of Contents
Abstract
Release Manager and Crew
Release Schedule
Maintenance Releases
Features for 3.1
Footnotes
Copyright
Abstra... | Final | PEP 375 – Python 3.1 Release Schedule | Informational | This document describes the development and release schedule for Python 3.1.
The schedule primarily concerns itself with PEP-sized items. Small features may
be added up to and including the first beta release. Bugs may be fixed until
the final release. |
PEP 376 – Database of Installed Python Distributions
Author:
Tarek Ziadé <tarek at ziade.org>
Status:
Final
Type:
Standards Track
Topic:
Packaging
Created:
22-Feb-2009
Python-Version:
2.7, 3.2
Post-History:
22-Jun-2009
Table of Contents
Abstract
Rationale
How distributions are installed
Uninstall information
What ... | Final | PEP 376 – Database of Installed Python Distributions | Standards Track | The goal of this PEP is to provide a standard infrastructure to manage
project distributions installed on a system, so all tools that are
installing or removing projects are interoperable. |
PEP 377 – Allow __enter__() methods to skip the statement body
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Rejected
Type:
Standards Track
Created:
08-Mar-2009
Python-Version:
2.7, 3.1
Post-History:
08-Mar-2009
Table of Contents
Abstract
PEP Rejection
Proposed Change
Rationale for Change
Performance Impa... | Rejected | PEP 377 – Allow __enter__() methods to skip the statement body | Standards Track | This PEP proposes a backwards compatible mechanism that allows __enter__()
methods to skip the body of the associated with statement. The lack of
this ability currently means the contextlib.contextmanager decorator
is unable to fulfil its specification of being able to turn arbitrary
code into a context manager by movi... |
PEP 379 – Adding an Assignment Expression
Author:
Jervis Whitley <jervisau at gmail.com>
Status:
Withdrawn
Type:
Standards Track
Created:
14-Mar-2009
Python-Version:
2.7, 3.2
Post-History:
Table of Contents
Abstract
Motivation and Summary
Use Cases
Specification
Examples from the Standard Library
Examples
Referen... | Withdrawn | PEP 379 – Adding an Assignment Expression | Standards Track | This PEP adds a new assignment expression to the Python language
to make it possible to assign the result of an expression in
almost any place. The new expression will allow the assignment of
the result of an expression at first use (in a comparison for
example). |
PEP 380 – Syntax for Delegating to a Subgenerator
Author:
Gregory Ewing <greg.ewing at canterbury.ac.nz>
Status:
Final
Type:
Standards Track
Created:
13-Feb-2009
Python-Version:
3.3
Post-History:
Resolution:
Python-Dev message
Table of Contents
Abstract
PEP Acceptance
Motivation
Proposal
Enhancements to StopItera... | Final | PEP 380 – Syntax for Delegating to a Subgenerator | Standards Track | A syntax is proposed for a generator to delegate part of its
operations to another generator. This allows a section of code
containing ‘yield’ to be factored out and placed in another generator.
Additionally, the subgenerator is allowed to return with a value, and
the value is made available to the delegating generato... |
PEP 381 – Mirroring infrastructure for PyPI
Author:
Tarek Ziadé <tarek at ziade.org>, Martin von Löwis <martin at v.loewis.de>
Status:
Withdrawn
Type:
Standards Track
Topic:
Packaging
Created:
21-Mar-2009
Post-History:
Table of Contents
Abstract
PEP Withdrawal
Rationale
Mirror listing and registering
Statistics p... | Withdrawn | PEP 381 – Mirroring infrastructure for PyPI | Standards Track | This PEP describes a mirroring infrastructure for PyPI. |
PEP 382 – Namespace Packages
Author:
Martin von Löwis <martin at v.loewis.de>
Status:
Rejected
Type:
Standards Track
Created:
02-Apr-2009
Python-Version:
3.2
Post-History:
Table of Contents
Rejection Notice
Abstract
Terminology
Namespace packages today
Rationale
Specification
Impact on Import Hooks
Discussion
R... | Rejected | PEP 382 – Namespace Packages | Standards Track | Namespace packages are a mechanism for splitting a single Python
package across multiple directories on disk. In current Python
versions, an algorithm to compute the packages __path__ must be
formulated. With the enhancement proposed here, the import machinery
itself will construct the list of directories that make up ... |
PEP 383 – Non-decodable Bytes in System Character Interfaces
Author:
Martin von Löwis <martin at v.loewis.de>
Status:
Final
Type:
Standards Track
Created:
22-Apr-2009
Python-Version:
3.1
Post-History:
Table of Contents
Abstract
Rationale
Specification
Discussion
References
Copyright
Abstract
File names, enviro... | Final | PEP 383 – Non-decodable Bytes in System Character Interfaces | Standards Track | File names, environment variables, and command line arguments are
defined as being character data in POSIX; the C APIs however allow
passing arbitrary bytes - whether these conform to a certain encoding
or not. This PEP proposes a means of dealing with such irregularities
by embedding the bytes in character strings in ... |
PEP 384 – Defining a Stable ABI
Author:
Martin von Löwis <martin at v.loewis.de>
Status:
Final
Type:
Standards Track
Created:
17-May-2009
Python-Version:
3.2
Post-History:
Table of Contents
Abstract
Rationale
Specification
Terminology
Header Files and Preprocessor Definitions
Structures
Type Objects
typedefs
Func... | Final | PEP 384 – Defining a Stable ABI | Standards Track | Currently, each feature release introduces a new name for the
Python DLL on Windows, and may cause incompatibilities for extension
modules on Unix. This PEP proposes to define a stable set of API
functions which are guaranteed to be available for the lifetime
of Python 3, and which will also remain binary-compatible ac... |
PEP 386 – Changing the version comparison module in Distutils
Author:
Tarek Ziadé <tarek at ziade.org>
Status:
Superseded
Type:
Standards Track
Topic:
Packaging
Created:
04-Jun-2009
Superseded-By:
440
Table of Contents
Abstract
Motivation
Requisites and current status
Distutils
Setuptools
Caveats of existing syste... | Superseded | PEP 386 – Changing the version comparison module in Distutils | Standards Track | Note: This PEP has been superseded by the version identification and
dependency specification scheme defined in PEP 440. |
PEP 389 – argparse - New Command Line Parsing Module
Author:
Steven Bethard <steven.bethard at gmail.com>
Status:
Final
Type:
Standards Track
Created:
25-Sep-2009
Python-Version:
2.7, 3.2
Post-History:
27-Sep-2009, 24-Oct-2009
Table of Contents
Acceptance
Abstract
Motivation
Why aren’t getopt and optparse enough?
... | Final | PEP 389 – argparse - New Command Line Parsing Module | Standards Track | This PEP proposes inclusion of the argparse [1] module in the Python
standard library in Python 2.7 and 3.2. |
PEP 391 – Dictionary-Based Configuration For Logging
Author:
Vinay Sajip <vinay_sajip at red-dove.com>
Status:
Final
Type:
Standards Track
Created:
15-Oct-2009
Python-Version:
2.7, 3.2
Post-History:
Table of Contents
Abstract
Rationale
Specification
Naming
API
Dictionary Schema - Overview
Object connections
User-... | Final | PEP 391 – Dictionary-Based Configuration For Logging | Standards Track | This PEP describes a new way of configuring logging using a dictionary
to hold configuration information. |
PEP 392 – Python 3.2 Release Schedule
Author:
Georg Brandl <georg at python.org>
Status:
Final
Type:
Informational
Topic:
Release
Created:
30-Dec-2009
Python-Version:
3.2
Table of Contents
Abstract
Release Manager and Crew
3.2 Lifespan
Release Schedule
3.2 schedule
3.2.1 schedule
3.2.2 schedule
3.2.3 schedule
3.2.... | Final | PEP 392 – Python 3.2 Release Schedule | Informational | This document describes the development and release schedule for the
Python 3.2 series. The schedule primarily concerns itself with PEP-sized
items. |
PEP 393 – Flexible String Representation
Author:
Martin von Löwis <martin at v.loewis.de>
Status:
Final
Type:
Standards Track
Created:
24-Jan-2010
Python-Version:
3.3
Post-History:
Table of Contents
Abstract
Rationale
Specification
String Creation
String Access
New API
Stable ABI
GDB Debugging Hooks
Deprecations,... | Final | PEP 393 – Flexible String Representation | Standards Track | 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 UCS-4 on all
systems. For compatibility with existing APIs, several r... |
PEP 394 – The “python” Command on Unix-Like Systems
Author:
Kerrick Staley <mail at kerrickstaley.com>,
Alyssa Coghlan <ncoghlan at gmail.com>,
Barry Warsaw <barry at python.org>,
Petr Viktorin <encukou at gmail.com>,
Miro Hrončok <miro at hroncok.cz>,
Carol Willing <willingc at gmail.com>
Status:
Active
Type:
Inform... | Active | PEP 394 – The “python” Command on Unix-Like Systems | Informational | 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.
End users may be unaware of this inconsistency across Unix-like sys... |
PEP 395 – Qualified Names for Modules
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Withdrawn
Type:
Standards Track
Created:
04-Mar-2011
Python-Version:
3.4
Post-History:
05-Mar-2011, 19-Nov-2011
Table of Contents
PEP Withdrawal
Abstract
Relationship with Other PEPs
What’s in a __name__?
Traps for the U... | Withdrawn | PEP 395 – Qualified Names for Modules | Standards Track | This PEP proposes new mechanisms that eliminate some longstanding traps for
the unwary when dealing with Python’s import system, as well as serialisation
and introspection of functions and classes. |
PEP 396 – Module Version Numbers
Author:
Barry Warsaw <barry at python.org>
Status:
Rejected
Type:
Informational
Topic:
Packaging
Created:
16-Mar-2011
Post-History:
05-Apr-2011
Table of Contents
Abstract
PEP Rejection
User Stories
Rationale
Specification
Examples
Deriving
Classic distutils
Distutils2
PEP 376 met... | Rejected | PEP 396 – Module Version Numbers | Informational | Given that it is useful and common to specify version numbers for
Python modules, and given that different ways of doing this have grown
organically within the Python community, it is useful to establish
standard conventions for module authors to adhere to and reference.
This informational PEP describes best practices ... |
PEP 397 – Python launcher for Windows
Author:
Mark Hammond <mhammond at skippinet.com.au>,
Martin von Löwis <martin at v.loewis.de>
Status:
Final
Type:
Standards Track
Created:
15-Mar-2011
Python-Version:
3.3
Post-History:
21-Jul-2011, 17-May-2011, 15-Mar-2011
Resolution:
Python-Dev message
Table of Contents
Abstr... | Final | PEP 397 – Python launcher for Windows | Standards Track | This PEP describes a Python launcher for the Windows platform. A
Python launcher is a single executable which uses a number of
heuristics to locate a Python executable and launch it with a
specified command line. |
PEP 398 – Python 3.3 Release Schedule
Author:
Georg Brandl <georg at python.org>
Status:
Final
Type:
Informational
Topic:
Release
Created:
23-Mar-2011
Python-Version:
3.3
Table of Contents
Abstract
Release Manager and Crew
3.3 Lifespan
Release Schedule
3.3.0 schedule
3.3.1 schedule
3.3.2 schedule
3.3.3 schedule
3.... | Final | PEP 398 – Python 3.3 Release Schedule | Informational | This document describes the development and release schedule for
Python 3.3. The schedule primarily concerns itself with PEP-sized
items. |
PEP 399 – Pure Python/C Accelerator Module Compatibility Requirements
Author:
Brett Cannon <brett at python.org>
Status:
Final
Type:
Informational
Created:
04-Apr-2011
Python-Version:
3.3
Post-History:
04-Apr-2011, 12-Apr-2011, 17-Jul-2011, 15-Aug-2011, 01-Jan-2013
Table of Contents
Abstract
Rationale
Details
Copy... | Final | PEP 399 – Pure Python/C Accelerator Module Compatibility Requirements | Informational | The Python standard library under CPython contains various instances
of modules implemented in both pure Python and C (either entirely or
partially). This PEP requires that in these instances that the
C code must pass the test suite used for the pure Python code
so as to act as much as a drop-in replacement as reasonab... |
PEP 400 – Deprecate codecs.StreamReader and codecs.StreamWriter
Author:
Victor Stinner <vstinner at python.org>
Status:
Deferred
Type:
Standards Track
Created:
28-May-2011
Python-Version:
3.3
Table of Contents
Abstract
PEP Deferral
Motivation
Rationale
StreamReader and StreamWriter issues
TextIOWrapper features
Te... | Deferred | PEP 400 – Deprecate codecs.StreamReader and codecs.StreamWriter | Standards Track | io.TextIOWrapper and codecs.StreamReaderWriter offer the same API
[1]. TextIOWrapper has more features and is faster than
StreamReaderWriter. Duplicate code means that bugs should be fixed
twice and that we may have subtle differences between the two
implementations. |
PEP 401 – BDFL Retirement
Author:
Barry Warsaw, Brett Cannon
Status:
April Fool!
Type:
Process
Created:
01-Apr-2009
Post-History:
01-Apr-2009
Table of Contents
Abstract
Rationale
Official Acts of the FLUFL
References
Copyright
Abstract
The BDFL, having shepherded Python development for 20 years,
officially anno... | April Fool! | PEP 401 – BDFL Retirement | Process | The BDFL, having shepherded Python development for 20 years,
officially announces his retirement, effective immediately. Following
a unanimous vote, his replacement is named. |
PEP 402 – Simplified Package Layout and Partitioning
Author:
Phillip J. Eby
Status:
Rejected
Type:
Standards Track
Topic:
Packaging
Created:
12-Jul-2011
Python-Version:
3.3
Post-History:
20-Jul-2011
Replaces:
382
Table of Contents
Rejection Notice
Abstract
The Problem
The Solution
A Thought Experiment
Self-Contain... | Rejected | PEP 402 – Simplified Package Layout and Partitioning | Standards Track | This PEP proposes an enhancement to Python’s package importing
to: |
PEP 403 – General purpose decorator clause (aka “@in” clause)
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Deferred
Type:
Standards Track
Created:
13-Oct-2011
Python-Version:
3.4
Post-History:
13-Oct-2011
Table of Contents
Abstract
Basic Examples
Proposal
Syntax Change
Design Discussion
Background
Rela... | Deferred | PEP 403 – General purpose decorator clause (aka “@in” clause) | Standards Track | This PEP proposes the addition of a new @in decorator clause that makes
it possible to override the name binding step of a function or class
definition. |
PEP 404 – Python 2.8 Un-release Schedule
Author:
Barry Warsaw <barry at python.org>
Status:
Final
Type:
Informational
Topic:
Release
Created:
09-Nov-2011
Python-Version:
2.8
Table of Contents
Abstract
Un-release Manager and Crew
Un-release Schedule
Official pronouncement
Upgrade path
And Now For Something Complete... | Final | PEP 404 – Python 2.8 Un-release Schedule | Informational | This document describes the un-development and un-release schedule for Python
2.8. |
PEP 406 – Improved Encapsulation of Import State
Author:
Alyssa Coghlan <ncoghlan at gmail.com>, Greg Slodkowicz <jergosh at gmail.com>
Status:
Withdrawn
Type:
Standards Track
Created:
04-Jul-2011
Python-Version:
3.4
Post-History:
31-Jul-2011, 13-Nov-2011, 04-Dec-2011
Table of Contents
Abstract
PEP Withdrawal
Rati... | Withdrawn | PEP 406 – Improved Encapsulation of Import State | Standards Track | This PEP proposes the introduction of a new ‘ImportEngine’ class as part of
importlib which would encapsulate all state related to importing modules
into a single object. Creating new instances of this object would then provide
an alternative to completely replacing the built-in implementation of the
import statement, ... |
PEP 407 – New release cycle and introducing long-term support versions
Author:
Antoine Pitrou <solipsis at pitrou.net>,
Georg Brandl <georg at python.org>,
Barry Warsaw <barry at python.org>
Status:
Deferred
Type:
Process
Created:
12-Jan-2012
Post-History:
17-Jan-2012
Table of Contents
Abstract
Scope
Proposal
Peri... | Deferred | PEP 407 – New release cycle and introducing long-term support versions | Process | Finding a release cycle for an open-source project is a delicate
exercise in managing mutually contradicting constraints: developer
manpower, availability of release management volunteers, ease of
maintenance for users and third-party packagers, quick availability of
new features (and behavioural changes), availability... |
PEP 408 – Standard library __preview__ package
Author:
Alyssa Coghlan <ncoghlan at gmail.com>,
Eli Bendersky <eliben at gmail.com>
Status:
Rejected
Type:
Standards Track
Created:
07-Jan-2012
Python-Version:
3.3
Post-History:
27-Jan-2012
Resolution:
Python-Dev message
Table of Contents
Abstract
PEP Rejection
Propos... | Rejected | PEP 408 – Standard library __preview__ package | Standards Track | The process of including a new module into the Python standard library is
hindered by the API lock-in and promise of backward compatibility implied by
a module being formally part of Python. This PEP proposes a transitional
state for modules - inclusion in a special __preview__ package for the
duration of a minor rele... |
PEP 409 – Suppressing exception context
Author:
Ethan Furman <ethan at stoneleaf.us>
Status:
Final
Type:
Standards Track
Created:
26-Jan-2012
Python-Version:
3.3
Post-History:
30-Aug-2002, 01-Feb-2012, 03-Feb-2012
Superseded-By:
415
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Alternatives
P... | Final | PEP 409 – Suppressing exception context | Standards Track | One of the open issues from PEP 3134 is suppressing context: currently
there is no way to do it. This PEP proposes one. |
PEP 410 – Use decimal.Decimal type for timestamps
Author:
Victor Stinner <vstinner at python.org>
Status:
Rejected
Type:
Standards Track
Created:
01-Feb-2012
Python-Version:
3.3
Resolution:
Python-Dev message
Table of Contents
Rejection Notice
Abstract
Rationale
Specification
Backwards Compatibility
Objection: clo... | Rejected | PEP 410 – Use decimal.Decimal type for timestamps | Standards Track | Decimal becomes the official type for high-resolution timestamps to make Python
support new functions using a nanosecond resolution without loss of precision. |
PEP 411 – Provisional packages in the Python standard library
Author:
Alyssa Coghlan <ncoghlan at gmail.com>,
Eli Bendersky <eliben at gmail.com>
Status:
Superseded
Type:
Informational
Created:
10-Feb-2012
Python-Version:
3.3
Post-History:
10-Feb-2012, 24-Mar-2012
Table of Contents
Abstract
Proposal - a documented... | Superseded | PEP 411 – Provisional packages in the Python standard library | Informational | The process of including a new package into the Python standard library is
hindered by the API lock-in and promise of backward compatibility implied by
a package being formally part of Python. This PEP describes a methodology
for marking a standard library package “provisional” for the period of a single
feature relea... |
PEP 412 – Key-Sharing Dictionary
Author:
Mark Shannon <mark at hotpy.org>
Status:
Final
Type:
Standards Track
Created:
08-Feb-2012
Python-Version:
3.3
Post-History:
08-Feb-2012
Table of Contents
Abstract
Motivation
Behaviour
Performance
Memory Usage
Speed
Implementation
Split-Table dictionaries
Combined-Table di... | Final | PEP 412 – Key-Sharing Dictionary | Standards Track | This PEP proposes a change in the implementation of the builtin
dictionary type dict. The new implementation allows dictionaries
which are used as attribute dictionaries (the __dict__ attribute
of an object) to share keys with other attribute dictionaries of
instances of the same class. |
PEP 413 – Faster evolution of the Python Standard Library
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Withdrawn
Type:
Process
Created:
24-Feb-2012
Post-History:
24-Feb-2012, 25-Feb-2012
Table of Contents
PEP Withdrawal
Abstract
Rationale
Proposal
Release Cycle
Programmatic Version Identification
Securit... | Withdrawn | PEP 413 – Faster evolution of the Python Standard Library | Process | This PEP proposes the adoption of a separate versioning scheme for the
standard library (distinct from, but coupled to, the existing language
versioning scheme) that allows accelerated releases of the Python standard
library, while maintaining (or even slowing down) the current rate of
change in the core language defin... |
PEP 414 – Explicit Unicode Literal for Python 3.3
Author:
Armin Ronacher <armin.ronacher at active-4.com>,
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Final
Type:
Standards Track
Created:
15-Feb-2012
Python-Version:
3.3
Post-History:
28-Feb-2012, 04-Mar-2012
Resolution:
Python-Dev message
Table of Contents
Abst... | Final | PEP 414 – Explicit Unicode Literal for Python 3.3 | Standards Track | This document proposes the reintegration of an explicit unicode literal
from Python 2.x to the Python 3.x language specification, in order to
reduce the volume of changes needed when porting Unicode-aware
Python 2 applications to Python 3. |
PEP 416 – Add a frozendict builtin type
Author:
Victor Stinner <vstinner at python.org>
Status:
Rejected
Type:
Standards Track
Created:
29-Feb-2012
Python-Version:
3.3
Table of Contents
Rejection Notice
Abstract
Rationale
Constraints
Implementation
Recipe: hashable dict
Objections
Alternative: dictproxy
Existing i... | Rejected | PEP 416 – Add a frozendict builtin type | Standards Track | Add a new frozendict builtin type. |
PEP 417 – Including mock in the Standard Library
Author:
Michael Foord <michael at python.org>
Status:
Final
Type:
Standards Track
Created:
12-Mar-2012
Python-Version:
3.3
Post-History:
12-Mar-2012
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Background
Open Issues
References
Copyright
Ab... | Final | PEP 417 – Including mock in the Standard Library | Standards Track | This PEP proposes adding the mock [1] testing library
to the Python standard library as unittest.mock. |
PEP 418 – Add monotonic time, performance counter, and process time functions
Author:
Cameron Simpson <cs at cskk.id.au>,
Jim J. Jewett <jimjjewett at gmail.com>,
Stephen J. Turnbull <stephen at xemacs.org>,
Victor Stinner <vstinner at python.org>
Status:
Final
Type:
Standards Track
Created:
26-Mar-2012
Python-Versio... | Final | PEP 418 – Add monotonic time, performance counter, and process time functions | Standards Track | This PEP proposes to add time.get_clock_info(name),
time.monotonic(), time.perf_counter() and
time.process_time() functions to Python 3.3. |
PEP 419 – Protecting cleanup statements from interruptions
Author:
Paul Colomiets <paul at colomiets.name>
Status:
Deferred
Type:
Standards Track
Created:
06-Apr-2012
Python-Version:
3.3
Table of Contents
Abstract
PEP Deferral
Rationale
Coroutine Use Case
Specification
Frame Flag ‘f_in_cleanup’
Function ‘sys.set... | Deferred | PEP 419 – Protecting cleanup statements from interruptions | Standards Track | This PEP proposes a way to protect Python code from being interrupted
inside a finally clause or during context manager cleanup. |
PEP 420 – Implicit Namespace Packages
Author:
Eric V. Smith <eric at trueblade.com>
Status:
Final
Type:
Standards Track
Created:
19-Apr-2012
Python-Version:
3.3
Post-History:
Resolution:
Python-Dev message
Table of Contents
Abstract
Terminology
Namespace packages today
Rationale
Specification
Dynamic path computa... | Final | PEP 420 – Implicit Namespace Packages | Standards Track | Namespace packages are a mechanism for splitting a single Python package
across multiple directories on disk. In current Python versions, an algorithm
to compute the packages __path__ must be formulated. With the enhancement
proposed here, the import machinery itself will construct the list of
directories that make u... |
PEP 422 – Simpler customisation of class creation
Author:
Alyssa Coghlan <ncoghlan at gmail.com>,
Daniel Urban <urban.dani+py at gmail.com>
Status:
Withdrawn
Type:
Standards Track
Created:
05-Jun-2012
Python-Version:
3.5
Post-History:
05-Jun-2012, 10-Feb-2013
Table of Contents
Abstract
PEP Withdrawal
Background
Pr... | Withdrawn | PEP 422 – 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 424 – A method for exposing a length hint
Author:
Alex Gaynor <alex.gaynor at gmail.com>
Status:
Final
Type:
Standards Track
Created:
14-Jul-2012
Python-Version:
3.4
Post-History:
15-Jul-2012
Table of Contents
Abstract
Specification
Rationale
Copyright
Abstract
CPython currently defines a __length_hint__ me... | Final | PEP 424 – A method for exposing a length hint | Standards Track | CPython currently defines a __length_hint__ method on several
types, such as various iterators. This method is then used by various
other functions (such as list) to presize lists based on the
estimate returned by __length_hint__. Types which are not sized,
and thus should not define __len__, can then define
__length... |
PEP 428 – The pathlib module – object-oriented filesystem paths
Author:
Antoine Pitrou <solipsis at pitrou.net>
Status:
Final
Type:
Standards Track
Created:
30-Jul-2012
Python-Version:
3.4
Post-History:
05-Oct-2012
Resolution:
Python-Dev message
Table of Contents
Abstract
Related work
Implementation
Why an object-... | Final | PEP 428 – The pathlib module – object-oriented filesystem paths | Standards Track | This PEP proposes the inclusion of a third-party module, pathlib, in
the standard library. The inclusion is proposed under the provisional
label, as described in PEP 411. Therefore, API changes can be done,
either as part of the PEP process, or after acceptance in the standard
library (and until the provisional label... |
PEP 429 – Python 3.4 Release Schedule
Author:
Larry Hastings <larry at hastings.org>
Status:
Final
Type:
Informational
Topic:
Release
Created:
17-Oct-2012
Python-Version:
3.4
Table of Contents
Abstract
Release Manager and Crew
Release Schedule
Features for 3.4
Copyright
Abstract
This document describes the deve... | Final | PEP 429 – Python 3.4 Release Schedule | Informational | This document describes the development and release schedule for
Python 3.4. The schedule primarily concerns itself with PEP-sized
items. |
PEP 433 – Easier suppression of file descriptor inheritance
Author:
Victor Stinner <vstinner at python.org>
Status:
Superseded
Type:
Standards Track
Created:
10-Jan-2013
Python-Version:
3.4
Superseded-By:
446
Table of Contents
Abstract
Rationale
Status in Python 3.3
Inherited file descriptors issues
Security
Atomi... | Superseded | PEP 433 – Easier suppression of file descriptor inheritance | Standards Track | Add a new optional cloexec parameter on functions creating file
descriptors, add different ways to change default values of this
parameter, and add four new functions: |
PEP 435 – Adding an Enum type to the Python standard library
Author:
Barry Warsaw <barry at python.org>,
Eli Bendersky <eliben at gmail.com>,
Ethan Furman <ethan at stoneleaf.us>
Status:
Final
Type:
Standards Track
Created:
23-Feb-2013
Python-Version:
3.4
Post-History:
23-Feb-2013, 02-May-2013
Replaces:
354
Resolutio... | Final | PEP 435 – Adding an Enum type to the Python standard library | Standards Track | This PEP proposes adding an enumeration type to the Python standard library. |
PEP 437 – A DSL for specifying signatures, annotations and argument converters
Author:
Stefan Krah <skrah at bytereef.org>
Status:
Rejected
Type:
Standards Track
Created:
11-Mar-2013
Python-Version:
3.4
Post-History:
Resolution:
Python-Dev message
Table of Contents
Abstract
Rejection Notice
Rationale
Scope
DSL ov... | Rejected | PEP 437 – A DSL for specifying signatures, annotations and argument converters | Standards Track | The Python C-API currently has no mechanism for specifying and auto-generating
function signatures, annotations or custom argument converters. |
PEP 446 – Make newly created file descriptors non-inheritable
Author:
Victor Stinner <vstinner at python.org>
Status:
Final
Type:
Standards Track
Created:
05-Aug-2013
Python-Version:
3.4
Replaces:
433
Table of Contents
Abstract
Rationale
Inheritance of File Descriptors
Inheritance of File Descriptors on Windows
On... | Final | PEP 446 – Make newly created file descriptors non-inheritable | Standards Track | Leaking file descriptors in child processes causes various annoying
issues and is a known major security vulnerability. Using the
subprocess module with the close_fds parameter set to True is
not possible in all cases. |
PEP 447 – Add __getdescriptor__ method to metaclass
Author:
Ronald Oussoren <ronaldoussoren at mac.com>
Status:
Deferred
Type:
Standards Track
Created:
12-Jun-2013
Post-History:
02-Jul-2013, 15-Jul-2013, 29-Jul-2013, 22-Jul-2015
Table of Contents
Abstract
PEP Status
Rationale
Background
The superclass attribute ... | Deferred | PEP 447 – Add __getdescriptor__ method to metaclass | Standards Track | Currently object.__getattribute__ and super.__getattribute__ peek
in the __dict__ of classes on the MRO for a class when looking for
an attribute. This PEP adds an optional __getdescriptor__ method to
a metaclass that replaces this behavior and gives more control over attribute
lookup, especially when using a super obj... |
PEP 450 – Adding A Statistics Module To The Standard Library
Author:
Steven D’Aprano <steve at pearwood.info>
Status:
Final
Type:
Standards Track
Created:
01-Aug-2013
Python-Version:
3.4
Post-History:
13-Sep-2013
Table of Contents
Abstract
Rationale
Comparison To Other Languages/Packages
R
C#
Ruby
PHP
Delphi
GNU S... | Final | PEP 450 – Adding A Statistics Module To The Standard Library | Standards Track | This PEP proposes the addition of a module for common statistics functions such
as mean, median, variance and standard deviation to the Python standard
library. See also http://bugs.python.org/issue18606 |
PEP 452 – API for Cryptographic Hash Functions v2.0
Author:
A.M. Kuchling <amk at amk.ca>, Christian Heimes <christian at python.org>
Status:
Final
Type:
Informational
Created:
15-Aug-2013
Post-History:
Replaces:
247
Table of Contents
Abstract
Specification
Rationale
Changes from Version 1.0 to Version 2.0
Recomm... | Final | PEP 452 – API for Cryptographic Hash Functions v2.0 | Informational | There are several different modules available that implement
cryptographic hashing algorithms such as MD5 or SHA. This
document specifies a standard API for such algorithms, to make it
easier to switch between different implementations. |
PEP 460 – Add binary interpolation and formatting
Author:
Antoine Pitrou <solipsis at pitrou.net>
Status:
Withdrawn
Type:
Standards Track
Created:
06-Jan-2014
Python-Version:
3.5
Table of Contents
Abstract
Rationale
Binary formatting features
Supported features
Unsupported features
Criticisms
Other proposals
A n... | Withdrawn | PEP 460 – Add binary interpolation and formatting | Standards Track | This PEP proposes to add minimal formatting operations to bytes and
bytearray objects. The proposed additions are: |
PEP 461 – Adding % formatting to bytes and bytearray
Author:
Ethan Furman <ethan at stoneleaf.us>
Status:
Final
Type:
Standards Track
Created:
13-Jan-2014
Python-Version:
3.5
Post-History:
14-Jan-2014, 15-Jan-2014, 17-Jan-2014, 22-Feb-2014, 25-Mar-2014,
27-Mar-2014
Resolution:
Python-Dev message
Table of Contents
... | Final | PEP 461 – Adding % formatting to bytes and bytearray | Standards Track | This PEP proposes adding % formatting operations similar to Python 2’s str
type to bytes and bytearray [1] [2]. |
PEP 462 – Core development workflow automation for CPython
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Withdrawn
Type:
Process
Requires:
474
Created:
23-Jan-2014
Post-History:
25-Jan-2014, 27-Jan-2014, 01-Feb-2015
Table of Contents
Abstract
PEP Withdrawal
Rationale for changes to the core development wo... | Withdrawn | PEP 462 – Core development workflow automation for CPython | Process | This PEP proposes investing in automation of several of the tedious,
time-consuming activities that are currently required for the core development
team to incorporate changes into CPython. This proposal is intended to
allow core developers to make more effective use of the time they have
available to contribute to CPy... |
PEP 463 – Exception-catching expressions
Author:
Chris Angelico <rosuav at gmail.com>
Status:
Rejected
Type:
Standards Track
Created:
15-Feb-2014
Python-Version:
3.5
Post-History:
20-Feb-2014, 16-Feb-2014
Resolution:
Python-Dev message
Table of Contents
Rejection Notice
Abstract
Motivation
Rationale
Proposal
Alter... | Rejected | PEP 463 – Exception-catching expressions | Standards Track | Just as PEP 308 introduced a means of value-based conditions in an
expression, this system allows exception-based conditions to be used
as part of an expression. |
PEP 465 – A dedicated infix operator for matrix multiplication
Author:
Nathaniel J. Smith <njs at pobox.com>
Status:
Final
Type:
Standards Track
Created:
20-Feb-2014
Python-Version:
3.5
Post-History:
13-Mar-2014
Resolution:
Python-Dev message
Table of Contents
Abstract
Specification
Motivation
Executive summary
Ba... | Final | PEP 465 – A dedicated infix operator for matrix multiplication | Standards Track | This PEP proposes a new binary operator to be used for matrix
multiplication, called @. (Mnemonic: @ is * for
mATrices.) |
PEP 466 – Network Security Enhancements for Python 2.7.x
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Final
Type:
Standards Track
Created:
23-Mar-2014
Python-Version:
2.7.9
Post-History:
23-Mar-2014, 24-Mar-2014, 25-Mar-2014, 26-Mar-2014, 16-Apr-2014
Resolution:
Python-Dev message
Table of Contents
Abstr... | Final | PEP 466 – Network Security Enhancements for Python 2.7.x | Standards Track | Most CPython tracker issues are classified as errors in behaviour or
proposed enhancements. Most patches to fix behavioural errors are
applied to all active maintenance branches. Enhancement patches are
restricted to the default branch that becomes the next Python version. |
PEP 469 – Migration of dict iteration code to Python 3
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Withdrawn
Type:
Standards Track
Created:
18-Apr-2014
Python-Version:
3.5
Post-History:
18-Apr-2014, 21-Apr-2014
Table of Contents
Abstract
PEP Withdrawal
Mapping iteration models
Lists as mutable snapshots... | Withdrawn | PEP 469 – Migration of dict iteration code to Python 3 | Standards Track | For Python 3, PEP 3106 changed the design of the dict builtin and the
mapping API in general to replace the separate list based and iterator based
APIs in Python 2 with a merged, memory efficient set and multiset view
based API. This new style of dict iteration was also added to the Python 2.7
dict type as a new set of... |
PEP 473 – Adding structured data to built-in exceptions
Author:
Sebastian Kreft <skreft at deezer.com>
Status:
Rejected
Type:
Standards Track
Created:
29-Mar-2014
Post-History:
Resolution:
Python-Dev message
Table of Contents
Abstract
Rationale
Examples
IndexError
KeyError
AttributeError
NameError
Other Cases
P... | Rejected | PEP 473 – Adding structured data to built-in exceptions | Standards Track | Exceptions like AttributeError, IndexError, KeyError,
LookupError, NameError, TypeError, and ValueError do not
provide all information required by programmers to debug and better understand
what caused them.
Furthermore, in some cases the messages even have slightly different formats,
which makes it really difficult fo... |
PEP 474 – Creating forge.python.org
Author:
Alyssa Coghlan <ncoghlan at gmail.com>
Status:
Withdrawn
Type:
Process
Created:
19-Jul-2014
Post-History:
19-Jul-2014, 08-Jan-2015, 01-Feb-2015
Table of Contents
Abstract
PEP Withdrawal
Proposal
Rationale
Intended Benefits
Sustaining Engineering Considerations
Personal M... | Withdrawn | PEP 474 – Creating forge.python.org | Process | This PEP proposes setting up a new PSF provided resource, forge.python.org,
as a location for maintaining various supporting repositories
(such as the repository for Python Enhancement Proposals) in a way that is
more accessible to new contributors, and easier to manage for core
developers. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.