text stringlengths 330 67k | status stringclasses 9
values | title stringlengths 18 80 | type stringclasses 3
values | abstract stringlengths 4 917 |
|---|---|---|---|---|
PEP 5 – Guidelines for Language Evolution
Author:
Paul Prescod <paul at prescod.net>
Status:
Superseded
Type:
Process
Created:
26-Oct-2000
Post-History:
Superseded-By:
387
Table of Contents
Abstract
Implementation Details
Scope
Steps For Introducing Backwards-Incompatible Features
Abstract
In the natural evolu... | Superseded | PEP 5 – Guidelines for Language Evolution | Process | In the natural evolution of programming languages it is sometimes
necessary to make changes that modify the behavior of older programs.
This PEP proposes a policy for implementing these changes in a manner
respectful of the installed base of Python users. |
PEP 6 – Bug Fix Releases
Author:
Aahz <aahz at pythoncraft.com>, Anthony Baxter <anthony at interlink.com.au>
Status:
Superseded
Type:
Process
Created:
15-Mar-2001
Post-History:
15-Mar-2001, 18-Apr-2001, 19-Aug-2004
Table of Contents
Abstract
Motivation
Prohibitions
Not-Quite-Prohibitions
Applicability of Prohibit... | Superseded | PEP 6 – Bug Fix Releases | Process | Python has historically had only a single fork of development, with
releases having the combined purpose of adding new features and
delivering bug fixes (these kinds of releases will be referred to as
“major releases”). This PEP describes how to fork off maintenance, or
bug fix, releases of old versions for the primar... |
PEP 10 – Voting Guidelines
Author:
Barry Warsaw <barry at python.org>
Status:
Active
Type:
Process
Created:
07-Mar-2002
Post-History:
07-Mar-2002
Table of Contents
Abstract
Rationale
Voting Scores
References
Copyright
Abstract
This PEP outlines the python-dev voting guidelines. These guidelines
serve to provid... | Active | PEP 10 – Voting Guidelines | Process | This PEP outlines the python-dev voting guidelines. These guidelines
serve to provide feedback or gauge the “wind direction” on a
particular proposal, idea, or feature. They don’t have a binding
force. |
PEP 11 – CPython platform support
Author:
Martin von Löwis <martin at v.loewis.de>,
Brett Cannon <brett at python.org>
Status:
Active
Type:
Process
Created:
07-Jul-2002
Post-History:
18-Aug-2007,
14-May-2014,
20-Feb-2015,
10-Mar-2022
Table of Contents
Abstract
Rationale
Support tiers
Tier 1
Tier 2
Tier 3
All other... | Active | PEP 11 – CPython platform support | Process | This PEP documents how an operating system (platform) becomes
supported in CPython, what platforms are currently supported, and
documents past support. |
PEP 12 – Sample reStructuredText PEP Template
Author:
David Goodger <goodger at python.org>,
Barry Warsaw <barry at python.org>,
Brett Cannon <brett at python.org>
Status:
Active
Type:
Process
Created:
05-Aug-2002
Post-History:
30-Aug-2002
Table of Contents
Abstract
Rationale
How to Use This Template
ReStructuredT... | Active | PEP 12 – Sample reStructuredText PEP Template | Process | This PEP provides a boilerplate or sample template for creating your
own reStructuredText PEPs. In conjunction with the content guidelines
in PEP 1, this should make it easy for you to conform your own
PEPs to the format outlined below. |
PEP 13 – Python Language Governance
Author:
The Python core team and community
Status:
Active
Type:
Process
Topic:
Governance
Created:
16-Dec-2018
Table of Contents
Abstract
Current steering council
Specification
The steering council
Composition
Mandate
Powers
Electing the council
Term
Vacancies
Conflicts of inter... | Active | PEP 13 – Python Language Governance | Process | This PEP defines the formal governance process for Python, and records
how this has changed over time. Currently, governance is based around
a steering council. The council has broad authority, which they seek
to exercise as rarely as possible. |
PEP 20 – The Zen of Python
Author:
Tim Peters <tim.peters at gmail.com>
Status:
Active
Type:
Informational
Created:
19-Aug-2004
Post-History:
22-Aug-2004
Table of Contents
Abstract
The Zen of Python
Easter Egg
References
Copyright
Abstract
Long time Pythoneer Tim Peters succinctly channels the BDFL’s guiding
pr... | Active | PEP 20 – The Zen of Python | Informational | Long time Pythoneer Tim Peters succinctly channels the BDFL’s guiding
principles for Python’s design into 20 aphorisms, only 19 of which
have been written down. |
PEP 101 – Doing Python Releases 101
Author:
Barry Warsaw <barry at python.org>, Guido van Rossum <guido at python.org>
Status:
Active
Type:
Informational
Created:
22-Aug-2001
Post-History:
Replaces:
102
Table of Contents
Abstract
Things You’ll Need
Types of Releases
How To Make A Release
What Next?
Moving to End-... | Active | PEP 101 – Doing Python Releases 101 | Informational | Making a Python release is a thrilling and crazy process. You’ve heard
the expression “herding cats”? Imagine trying to also saddle those
purring little creatures up, and ride them into town, with some of their
buddies firmly attached to your bare back, anchored by newly sharpened
claws. At least they’re cute, you r... |
PEP 102 – Doing Python Micro Releases
Author:
Anthony Baxter <anthony at interlink.com.au>,
Barry Warsaw <barry at python.org>,
Guido van Rossum <guido at python.org>
Status:
Superseded
Type:
Informational
Created:
09-Jan-2002
Post-History:
Superseded-By:
101
Table of Contents
Replacement Note
Abstract
How to Mak... | Superseded | PEP 102 – Doing Python Micro Releases | Informational | Making a Python release is an arduous process that takes a
minimum of half a day’s work even for an experienced releaser.
Until recently, most – if not all – of that burden was borne by
Guido himself. But several recent releases have been performed by
other folks, so this PEP attempts to collect, in one place, all
the... |
PEP 103 – Collecting information about git
Author:
Oleg Broytman <phd at phdru.name>
Status:
Withdrawn
Type:
Informational
Created:
01-Jun-2015
Post-History:
12-Sep-2015
Table of Contents
Withdrawal
Abstract
Documentation
Documentation for starters
Advanced documentation
Offline documentation
Quick start
Downloa... | Withdrawn | PEP 103 – Collecting information about git | Informational | This Informational PEP collects information about git. There is, of
course, a lot of documentation for git, so the PEP concentrates on
more complex (and more related to Python development) issues,
scenarios and examples. |
PEP 207 – Rich Comparisons
Author:
Guido van Rossum <guido at python.org>, David Ascher <DavidA at ActiveState.com>
Status:
Final
Type:
Standards Track
Created:
25-Jul-2000
Python-Version:
2.1
Post-History:
Table of Contents
Abstract
Motivation
Previous Work
Concerns
Proposed Resolutions
Implementation Proposal
C... | Final | PEP 207 – Rich Comparisons | Standards Track | This PEP proposes several new features for comparisons: |
PEP 208 – Reworking the Coercion Model
Author:
Neil Schemenauer <nas at arctrix.com>, Marc-André Lemburg <mal at lemburg.com>
Status:
Final
Type:
Standards Track
Created:
04-Dec-2000
Python-Version:
2.1
Post-History:
Table of Contents
Abstract
Rationale
Specification
Reference Implementation
Credits
Copyright
Ref... | Final | PEP 208 – Reworking the Coercion Model | Standards Track | Many Python types implement numeric operations. When the arguments of
a numeric operation are of different types, the interpreter tries to
coerce the arguments into a common type. The numeric operation is
then performed using this common type. This PEP proposes a new type
flag to indicate that arguments to a type’s ... |
PEP 209 – Multi-dimensional Arrays
Author:
Paul Barrett <barrett at stsci.edu>, Travis Oliphant <oliphant at ee.byu.edu>
Status:
Withdrawn
Type:
Standards Track
Created:
03-Jan-2001
Python-Version:
2.2
Post-History:
Table of Contents
Abstract
Motivation
Proposal
Design and Implementation
Open Issues
Implementatio... | Withdrawn | PEP 209 – Multi-dimensional Arrays | Standards Track | This PEP proposes a redesign and re-implementation of the
multi-dimensional array module, Numeric, to make it easier to add
new features and functionality to the module. Aspects of Numeric 2
that will receive special attention are efficient access to arrays
exceeding a gigabyte in size and composed of inhomogeneous da... |
PEP 215 – String Interpolation
Author:
Ka-Ping Yee <ping at zesty.ca>
Status:
Superseded
Type:
Standards Track
Created:
24-Jul-2000
Python-Version:
2.1
Post-History:
Superseded-By:
292
Table of Contents
Abstract
Copyright
Specification
Examples
Discussion
Security Issues
Implementation
References
Abstract
This... | Superseded | PEP 215 – String Interpolation | Standards Track | This document proposes a string interpolation feature for Python
to allow easier string formatting. The suggested syntax change
is the introduction of a ‘$’ prefix that triggers the special
interpretation of the ‘$’ character within a string, in a manner
reminiscent to the variable interpolation found in Unix shells,
... |
PEP 216 – Docstring Format
Author:
Moshe Zadka <moshez at zadka.site.co.il>
Status:
Rejected
Type:
Informational
Created:
31-Jul-2000
Post-History:
Superseded-By:
287
Table of Contents
Notice
Abstract
Perl Documentation
Java Documentation
Python Docstring Goals
High Level Solutions
Docstring Format Goals
Docstrin... | Rejected | PEP 216 – Docstring Format | Informational | Named Python objects, such as modules, classes and functions, have a
string attribute called __doc__. If the first expression inside
the definition is a literal string, that string is assigned
to the __doc__ attribute. |
PEP 217 – Display Hook for Interactive Use
Author:
Moshe Zadka <moshez at zadka.site.co.il>
Status:
Final
Type:
Standards Track
Created:
31-Jul-2000
Python-Version:
2.1
Post-History:
Table of Contents
Abstract
Interface
Solution
Jython Issues
Abstract
Python’s interactive mode is one of the implementation’s gr... | Final | PEP 217 – Display Hook for Interactive Use | Standards Track | Python’s interactive mode is one of the implementation’s great
strengths – being able to write expressions on the command line
and get back a meaningful output. However, the output function
cannot be all things to all people, and the current output
function too often falls short of this goal. This PEP describes a
way... |
PEP 220 – Coroutines, Generators, Continuations
Author:
Gordon McMillan <gmcm at hypernet.com>
Status:
Rejected
Type:
Informational
Created:
14-Aug-2000
Post-History:
Table of Contents
Abstract
Abstract
Demonstrates why the changes described in the stackless PEP are
desirable. A low-level continuations module... | Rejected | PEP 220 – Coroutines, Generators, Continuations | Informational | Demonstrates why the changes described in the stackless PEP are
desirable. A low-level continuations module exists. With it,
coroutines and generators and “green” threads can be written. A
higher level module that makes coroutines and generators easy to
create is desirable (and being worked on). The focus of this P... |
PEP 222 – Web Library Enhancements
Author:
A.M. Kuchling <amk at amk.ca>
Status:
Deferred
Type:
Standards Track
Created:
18-Aug-2000
Python-Version:
2.1
Post-History:
22-Dec-2000
Table of Contents
Abstract
Open Issues
New Modules
Major Changes to Existing Modules
Minor Changes to Existing Modules
Rejected Changes
... | Deferred | PEP 222 – Web Library Enhancements | Standards Track | This PEP proposes a set of enhancements to the CGI development
facilities in the Python standard library. Enhancements might be
new features, new modules for tasks such as cookie support, or
removal of obsolete code. |
PEP 223 – Change the Meaning of \x Escapes
Author:
Tim Peters <tim.peters at gmail.com>
Status:
Final
Type:
Standards Track
Created:
20-Aug-2000
Python-Version:
2.0
Post-History:
23-Aug-2000
Table of Contents
Abstract
Syntax
Semantics
Example
History and Rationale
Development and Discussion
Backward Compatibility
... | Final | PEP 223 – Change the Meaning of \x Escapes | Standards Track | Change \x escapes, in both 8-bit and Unicode strings, to consume
exactly the two hex digits following. The proposal views this as
correcting an original design flaw, leading to clearer expression
in all flavors of string, a cleaner Unicode story, better
compatibility with Perl regular expressions, and with minimal ris... |
PEP 226 – Python 2.1 Release Schedule
Author:
Jeremy Hylton <jeremy at alum.mit.edu>
Status:
Final
Type:
Informational
Topic:
Release
Created:
16-Oct-2000
Python-Version:
2.1
Post-History:
Table of Contents
Abstract
Release Schedule
Open issues for Python 2.0 beta 2
Guidelines for making changes for Python 2.1
Ge... | Final | PEP 226 – Python 2.1 Release Schedule | Informational | This document describes the post Python 2.0 development and
release schedule. According to this schedule, Python 2.1 will be
released in April of 2001. The schedule primarily concerns
itself with PEP-size items. Small bug fixes and changes will
occur up until the first beta release. |
PEP 227 – Statically Nested Scopes
Author:
Jeremy Hylton <jeremy at alum.mit.edu>
Status:
Final
Type:
Standards Track
Created:
01-Nov-2000
Python-Version:
2.1
Post-History:
Table of Contents
Abstract
Introduction
Specification
Discussion
Examples
Backwards compatibility
Compatibility of C API
locals() / vars()
Wa... | Final | PEP 227 – Statically Nested Scopes | Standards Track | This PEP describes the addition of statically nested scoping
(lexical scoping) for Python 2.2, and as a source level option
for python 2.1. In addition, Python 2.1 will issue warnings about
constructs whose meaning may change when this feature is enabled. |
PEP 228 – Reworking Python’s Numeric Model
Author:
Moshe Zadka <moshez at zadka.site.co.il>, Guido van Rossum <guido at python.org>
Status:
Withdrawn
Type:
Standards Track
Created:
04-Nov-2000
Post-History:
Table of Contents
Withdrawal
Abstract
Rationale
Other Numerical Models
Suggested Interface For Python’s Num... | Withdrawn | PEP 228 – Reworking Python’s Numeric Model | Standards Track | Today, Python’s numerical model is similar to the C numeric model:
there are several unrelated numerical types, and when operations
between numerical types are requested, coercions happen. While
the C rationale for the numerical model is that it is very similar
to what happens at the hardware level, that rationale doe... |
PEP 230 – Warning Framework
Author:
Guido van Rossum <guido at python.org>
Status:
Final
Type:
Standards Track
Created:
28-Nov-2000
Python-Version:
2.1
Post-History:
05-Nov-2000
Table of Contents
Abstract
Motivation
APIs For Issuing Warnings
Warnings Categories
The Warnings Filter
Warnings Output And Formatting Ho... | Final | PEP 230 – Warning Framework | Standards Track | This PEP proposes a C and Python level API, as well as command
line flags, to issue warning messages and control what happens to
them. This is mostly based on GvR’s proposal posted to python-dev
on 05-Nov-2000, with some ideas (such as using classes to
categorize warnings) merged in from Paul Prescod’s
counter-proposa... |
PEP 233 – Python Online Help
Author:
Paul Prescod <paul at prescod.net>
Status:
Deferred
Type:
Standards Track
Created:
11-Dec-2000
Python-Version:
2.1
Post-History:
Table of Contents
Abstract
Interactive use
Implementation
Built-in Topics
Security Issues
Abstract
This PEP describes a command-line driven onlin... | Deferred | PEP 233 – Python Online Help | Standards Track | This PEP describes a command-line driven online help facility for
Python. The facility should be able to build on existing
documentation facilities such as the Python documentation and
docstrings. It should also be extensible for new types and
modules. |
PEP 234 – Iterators
Author:
Ka-Ping Yee <ping at zesty.ca>, Guido van Rossum <guido at python.org>
Status:
Final
Type:
Standards Track
Created:
30-Jan-2001
Python-Version:
2.1
Post-History:
30-Apr-2001
Table of Contents
Abstract
C API Specification
Python API Specification
Dictionary Iterators
File Iterators
Ratio... | Final | PEP 234 – Iterators | Standards Track | This document proposes an iteration interface that objects can provide to
control the behaviour of for loops. Looping is customized by providing a
method that produces an iterator object. The iterator provides a get next
value operation that produces the next item in the sequence each time it is
called, raising an ex... |
PEP 237 – Unifying Long Integers and Integers
Author:
Moshe Zadka, Guido van Rossum
Status:
Final
Type:
Standards Track
Created:
11-Mar-2001
Python-Version:
2.2
Post-History:
16-Mar-2001, 14-Aug-2001, 23-Aug-2001
Table of Contents
Abstract
Rationale
Implementation
Incompatibilities
Literals
Built-in Functions
C AP... | Final | PEP 237 – Unifying Long Integers and Integers | Standards Track | Python currently distinguishes between two kinds of integers (ints): regular
or short ints, limited by the size of a C long (typically 32 or 64 bits), and
long ints, which are limited only by available memory. When operations on
short ints yield results that don’t fit in a C long, they raise an error.
There are some o... |
PEP 238 – Changing the Division Operator
Author:
Moshe Zadka <moshez at zadka.site.co.il>,
Guido van Rossum <guido at python.org>
Status:
Final
Type:
Standards Track
Created:
11-Mar-2001
Python-Version:
2.2
Post-History:
16-Mar-2001, 26-Jul-2001, 27-Jul-2001
Table of Contents
Abstract
Motivation
Variations
Alterna... | Final | PEP 238 – Changing the Division Operator | Standards Track | The current division (/) operator has an ambiguous meaning for numerical
arguments: it returns the floor of the mathematical result of division if the
arguments are ints or longs, but it returns a reasonable approximation of the
division result if the arguments are floats or complex. This makes
expressions expecting f... |
PEP 239 – Adding a Rational Type to Python
Author:
Christopher A. Craig <python-pep at ccraig.org>, Moshe Zadka <moshez at zadka.site.co.il>
Status:
Rejected
Type:
Standards Track
Created:
11-Mar-2001
Python-Version:
2.2
Post-History:
16-Mar-2001
Table of Contents
Abstract
BDFL Pronouncement
Rationale
RationalType... | Rejected | PEP 239 – Adding a Rational Type to Python | Standards Track | Python has no numeric type with the semantics of an unboundedly
precise rational number. This proposal explains the semantics of
such a type, and suggests builtin functions and literals to
support such a type. This PEP suggests no literals for rational
numbers; that is left for another PEP. |
PEP 240 – Adding a Rational Literal to Python
Author:
Christopher A. Craig <python-pep at ccraig.org>, Moshe Zadka <moshez at zadka.site.co.il>
Status:
Rejected
Type:
Standards Track
Created:
11-Mar-2001
Python-Version:
2.2
Post-History:
16-Mar-2001
Table of Contents
Abstract
BDFL Pronouncement
Rationale
Proposal
... | Rejected | PEP 240 – Adding a Rational Literal to Python | Standards Track | A different PEP suggests adding a builtin rational type to
Python. This PEP suggests changing the ddd.ddd float literal to a
rational in Python, and modifying non-integer division to return
it. |
PEP 242 – Numeric Kinds
Author:
Paul F. Dubois <paul at pfdubois.com>
Status:
Rejected
Type:
Standards Track
Created:
17-Mar-2001
Python-Version:
2.2
Post-History:
17-Apr-2001
Table of Contents
Abstract
Rationale
Supported Kinds of Ints and Floats
Kind Objects
Attributes of Module kinds
Complex Numbers
Examples
Op... | Rejected | PEP 242 – Numeric Kinds | Standards Track | This proposal gives the user optional control over the precision
and range of numeric computations so that a computation can be
written once and run anywhere with at least the desired precision
and range. It is backward compatible with existing code. The
meaning of decimal literals is clarified. |
PEP 246 – Object Adaptation
Author:
Alex Martelli <aleaxit at gmail.com>,
Clark C. Evans <cce at clarkevans.com>
Status:
Rejected
Type:
Standards Track
Created:
21-Mar-2001
Python-Version:
2.5
Post-History:
29-Mar-2001, 10-Jan-2005
Table of Contents
Rejection Notice
Abstract
Motivation
Requirements
Specification
I... | Rejected | PEP 246 – Object Adaptation | Standards Track | This proposal puts forth an extensible cooperative mechanism for
the adaptation of an incoming object to a context which expects an
object supporting a specific protocol (say a specific type, class,
or interface). |
PEP 247 – API for Cryptographic Hash Functions
Author:
A.M. Kuchling <amk at amk.ca>
Status:
Final
Type:
Informational
Created:
23-Mar-2001
Post-History:
20-Sep-2001
Table of Contents
Abstract
Specification
Rationale
Changes
Acknowledgements
Copyright
Abstract
There are several different modules available that ... | Final | PEP 247 – API for Cryptographic Hash Functions | 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 250 – Using site-packages on Windows
Author:
Paul Moore <p.f.moore at gmail.com>
Status:
Final
Type:
Standards Track
Created:
30-Mar-2001
Python-Version:
2.2
Post-History:
30-Mar-2001
Table of Contents
Abstract
Motivation
Implementation
Notes
Open Issues
Copyright
Abstract
The standard Python distribution i... | Final | PEP 250 – Using site-packages on Windows | Standards Track | The standard Python distribution includes a directory
Lib/site-packages, which is used on Unix platforms to hold
locally installed modules and packages. The site.py module
distributed with Python includes support for locating other
modules in the site-packages directory. |
PEP 251 – Python 2.2 Release Schedule
Author:
Barry Warsaw <barry at python.org>, Guido van Rossum <guido at python.org>
Status:
Final
Type:
Informational
Topic:
Release
Created:
17-Apr-2001
Python-Version:
2.2
Post-History:
14-Aug-2001
Table of Contents
Abstract
Release Schedule
Release Manager
Release Mechanics
... | Final | PEP 251 – Python 2.2 Release Schedule | Informational | This document describes the Python 2.2 development and release
schedule. The schedule primarily concerns itself with PEP-sized
items. Small bug fixes and changes will occur up until the first
beta release. |
PEP 252 – Making Types Look More Like Classes
Author:
Guido van Rossum <guido at python.org>
Status:
Final
Type:
Standards Track
Created:
19-Apr-2001
Python-Version:
2.2
Post-History:
Table of Contents
Abstract
Introduction
Introspection APIs
Specification of the class-based introspection API
Specification of the... | Final | PEP 252 – Making Types Look More Like Classes | Standards Track | This PEP proposes changes to the introspection API for types that
makes them look more like classes, and their instances more like
class instances. For example, type(x) will be equivalent to
x.__class__ for most built-in types. When C is x.__class__,
x.meth(a) will generally be equivalent to C.meth(x, a), and
C.__dic... |
PEP 253 – Subtyping Built-in Types
Author:
Guido van Rossum <guido at python.org>
Status:
Final
Type:
Standards Track
Created:
14-May-2001
Python-Version:
2.2
Post-History:
Table of Contents
Abstract
Introduction
About metatypes
Making a type a factory for its instances
Preparing a type for subtyping
Creating a s... | Final | PEP 253 – Subtyping Built-in Types | Standards Track | This PEP proposes additions to the type object API that will allow
the creation of subtypes of built-in types, in C and in Python. |
PEP 254 – Making Classes Look More Like Types
Author:
Guido van Rossum <guido at python.org>
Status:
Rejected
Type:
Standards Track
Created:
18-Jun-2001
Python-Version:
2.2
Post-History:
Table of Contents
Abstract
Status
Copyright
Abstract
This PEP has not been written yet. Watch this space!
Status
This PEP... | Rejected | PEP 254 – Making Classes Look More Like Types | Standards Track | This PEP has not been written yet. Watch this space! |
PEP 255 – Simple Generators
Author:
Neil Schemenauer <nas at arctrix.com>,
Tim Peters <tim.peters at gmail.com>,
Magnus Lie Hetland <magnus at hetland.org>
Status:
Final
Type:
Standards Track
Requires:
234
Created:
18-May-2001
Python-Version:
2.2
Post-History:
14-Jun-2001, 23-Jun-2001
Table of Contents
Abstract
Mo... | Final | PEP 255 – Simple Generators | Standards Track | This PEP introduces the concept of generators to Python, as well as a new
statement used in conjunction with them, the yield statement. |
PEP 259 – Omit printing newline after newline
Author:
Guido van Rossum <guido at python.org>
Status:
Rejected
Type:
Standards Track
Created:
11-Jun-2001
Python-Version:
2.2
Post-History:
11-Jun-2001
Table of Contents
Abstract
Problem
Proposed Solution
Scope
Risks
Implementation
Rejected
Copyright
Abstract
Curre... | Rejected | PEP 259 – Omit printing newline after newline | Standards Track | Currently, the print statement always appends a newline, unless a
trailing comma is used. This means that if we want to print data
that already ends in a newline, we get two newlines, unless
special precautions are taken. |
PEP 260 – Simplify xrange()
Author:
Guido van Rossum <guido at python.org>
Status:
Final
Type:
Standards Track
Created:
26-Jun-2001
Python-Version:
2.2
Post-History:
26-Jun-2001
Table of Contents
Abstract
Problem
Proposed Solution
Scope
Risks
Transition
Copyright
Abstract
This PEP proposes to strip the xrange()... | Final | PEP 260 – Simplify xrange() | Standards Track | This PEP proposes to strip the xrange() object from some rarely
used behavior like x[i:j] and x*n. |
PEP 261 – Support for “wide” Unicode characters
Author:
Paul Prescod <paul at prescod.net>
Status:
Final
Type:
Standards Track
Created:
27-Jun-2001
Python-Version:
2.2
Post-History:
27-Jun-2001
Table of Contents
Abstract
Glossary
Proposed Solution
Implementation
Notes
Rejected Suggestions
References
Copyright
A... | Final | PEP 261 – Support for “wide” Unicode characters | Standards Track | Python 2.1 unicode characters can have ordinals only up to 2**16 - 1.
This range corresponds to a range in Unicode known as the Basic
Multilingual Plane. There are now characters in Unicode that live
on other “planes”. The largest addressable character in Unicode
has the ordinal 17 * 2**16 - 1 (0x10ffff). For readabili... |
PEP 263 – Defining Python Source Code Encodings
Author:
Marc-André Lemburg <mal at lemburg.com>,
Martin von Löwis <martin at v.loewis.de>
Status:
Final
Type:
Standards Track
Created:
06-Jun-2001
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
Problem
Proposed Solution
Defining the Encoding
Examples
C... | Final | PEP 263 – Defining Python Source Code Encodings | Standards Track | This PEP proposes to introduce a syntax to declare the encoding of
a Python source file. The encoding information is then used by the
Python parser to interpret the file using the given encoding. Most
notably this enhances the interpretation of Unicode literals in
the source code and makes it possible to write Unicode ... |
PEP 264 – Future statements in simulated shells
Author:
Michael Hudson <mwh at python.net>
Status:
Final
Type:
Standards Track
Requires:
236
Created:
30-Jul-2001
Python-Version:
2.2
Post-History:
30-Jul-2001
Table of Contents
Abstract
Specification
Backward Compatibility
Forward Compatibility
Issues
Implementation... | Final | PEP 264 – Future statements in simulated shells | Standards Track | As noted in PEP 236, there is no clear way for “simulated
interactive shells” to simulate the behaviour of __future__
statements in “real” interactive shells, i.e. have __future__
statements’ effects last the life of the shell. |
PEP 265 – Sorting Dictionaries by Value
Author:
Grant Griffin <g2 at iowegian.com>
Status:
Rejected
Type:
Standards Track
Created:
08-Aug-2001
Python-Version:
2.2
Post-History:
Table of Contents
Abstract
BDFL Pronouncement
Motivation
Rationale
Implementation
Concerns
References
Copyright
Abstract
This PEP sugg... | Rejected | PEP 265 – Sorting Dictionaries by Value | Standards Track | This PEP suggests a “sort by value” operation for dictionaries.
The primary benefit would be in terms of “batteries included”
support for a common Python idiom which, in its current form, is
both difficult for beginners to understand and cumbersome for all
to implement. |
PEP 266 – Optimizing Global Variable/Attribute Access
Author:
Skip Montanaro <skip at pobox.com>
Status:
Withdrawn
Type:
Standards Track
Created:
13-Aug-2001
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
Introduction
Proposed Change
Threads
Rationale
Questions
What about threads? What if math.sin ... | Withdrawn | PEP 266 – Optimizing Global Variable/Attribute Access | Standards Track | The bindings for most global variables and attributes of other modules
typically never change during the execution of a Python program, but because
of Python’s dynamic nature, code which accesses such global objects must run
through a full lookup each time the object is needed. This PEP proposes a
mechanism that allow... |
PEP 267 – Optimized Access to Module Namespaces
Author:
Jeremy Hylton <jeremy at alum.mit.edu>
Status:
Deferred
Type:
Standards Track
Created:
23-May-2001
Python-Version:
2.2
Post-History:
Table of Contents
Deferral
Abstract
Introduction
DLict design
Compiler issues
Runtime model
Backwards compatibility
Related P... | Deferred | PEP 267 – Optimized Access to Module Namespaces | Standards Track | This PEP proposes a new implementation of global module namespaces
and the builtin namespace that speeds name resolution. The
implementation would use an array of object pointers for most
operations in these namespaces. The compiler would assign indices
for global variables and module attributes at compile time. |
PEP 268 – Extended HTTP functionality and WebDAV
Author:
Greg Stein <gstein at lyra.org>
Status:
Rejected
Type:
Standards Track
Created:
20-Aug-2001
Python-Version:
2.x
Post-History:
21-Aug-2001
Table of Contents
Rejection Notice
Abstract
Rationale
Specification
HTTP Authentication
Proxy Handling
WebDAV Features
... | Rejected | PEP 268 – Extended HTTP functionality and WebDAV | Standards Track | This PEP discusses new modules and extended functionality for Python’s
HTTP support. Notably, the addition of authenticated requests, proxy
support, authenticated proxy usage, and WebDAV capabilities. |
PEP 269 – Pgen Module for Python
Author:
Jonathan Riehl <jriehl at spaceship.com>
Status:
Deferred
Type:
Standards Track
Created:
24-Aug-2001
Python-Version:
2.2
Post-History:
Table of Contents
Abstract
Rationale
Specification
parseGrammarFile (fileName) -> AST
parseGrammarString (text) -> AST
buildParser (gramma... | Deferred | PEP 269 – Pgen Module for Python | Standards Track | Much like the parser module exposes the Python parser, this PEP
proposes that the parser generator used to create the Python
parser, pgen, be exposed as a module in Python. |
PEP 270 – uniq method for list objects
Author:
Jason Petrone <jp at demonseed.net>
Status:
Rejected
Type:
Standards Track
Created:
21-Aug-2001
Python-Version:
2.2
Post-History:
Table of Contents
Notice
Abstract
Rationale
Considerations
Reference Implementation
References
Copyright
Notice
This PEP is withdrawn ... | Rejected | PEP 270 – uniq method for list objects | Standards Track | This PEP proposes adding a method for removing duplicate elements to
the list object. |
PEP 271 – Prefixing sys.path by command line option
Author:
Frédéric B. Giacometti <fred at arakne.com>
Status:
Rejected
Type:
Standards Track
Created:
15-Aug-2001
Python-Version:
2.2
Post-History:
Table of Contents
Abstract
Rationale
Other Information
When to use this option
Reference Implementation
Copyright
... | Rejected | PEP 271 – Prefixing sys.path by command line option | Standards Track | At present, setting the PYTHONPATH environment variable is the
only method for defining additional Python module search
directories. |
PEP 272 – API for Block Encryption Algorithms v1.0
Author:
A.M. Kuchling <amk at amk.ca>
Status:
Final
Type:
Informational
Created:
18-Sep-2001
Post-History:
17-Apr-2002, 29-May-2002
Table of Contents
Abstract
Introduction
Specification
References
Changes
Acknowledgements
Copyright
Abstract
This document specif... | Final | PEP 272 – API for Block Encryption Algorithms v1.0 | Informational | This document specifies a standard API for secret-key block
encryption algorithms such as DES or Rijndael, making it easier to
switch between different algorithms and implementations. |
PEP 273 – Import Modules from Zip Archives
Author:
James C. Ahlstrom <jim at interet.com>
Status:
Final
Type:
Standards Track
Created:
11-Oct-2001
Python-Version:
2.3
Post-History:
26-Oct-2001
Table of Contents
Abstract
Note
Specification
Subdirectory Equivalence
Efficiency
zlib
Booting
Directory Imports
Benchmark... | Final | PEP 273 – Import Modules from Zip Archives | Standards Track | This PEP adds the ability to import Python modules
*.py, *.py[co] and packages from zip archives. The
same code is used to speed up normal directory imports
provided os.listdir is available. |
PEP 274 – Dict Comprehensions
Author:
Barry Warsaw <barry at python.org>
Status:
Final
Type:
Standards Track
Created:
25-Oct-2001
Python-Version:
2.7, 3.0
Post-History:
29-Oct-2001
Table of Contents
Abstract
Resolution
Proposed Solution
Rationale
Semantics
Examples
Implementation
Copyright
Abstract
PEP 202 intr... | Final | PEP 274 – Dict Comprehensions | Standards Track | PEP 202 introduces a syntactical extension to Python called the
“list comprehension”. This PEP proposes a similar syntactical
extension called the “dictionary comprehension” or “dict
comprehension” for short. You can use dict comprehensions in ways
very similar to list comprehensions, except that they produce
Python ... |
PEP 275 – Switching on Multiple Values
Author:
Marc-André Lemburg <mal at lemburg.com>
Status:
Rejected
Type:
Standards Track
Created:
10-Nov-2001
Python-Version:
2.6
Post-History:
Table of Contents
Rejection Notice
Abstract
Problem
Proposed Solutions
Solution 1: Optimizing if-elif-else
Solution 2: Adding a switc... | Rejected | PEP 275 – Switching on Multiple Values | Standards Track | This PEP proposes strategies to enhance Python’s performance
with respect to handling switching on a single variable having
one of multiple possible values. |
PEP 276 – Simple Iterator for ints
Author:
Jim Althoff <james_althoff at i2.com>
Status:
Rejected
Type:
Standards Track
Created:
12-Nov-2001
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
BDFL Pronouncement
Specification
Rationale
Backwards Compatibility
Issues
Implementation
Copyright
Abstract
P... | Rejected | PEP 276 – Simple Iterator for ints | Standards Track | Python 2.1 added new functionality to support iterators (PEP 234).
Iterators have proven to be useful and convenient in many coding
situations. It is noted that the implementation of Python’s
for-loop control structure uses the iterator protocol as of
release 2.1. It is also noted that Python provides iterators for
t... |
PEP 277 – Unicode file name support for Windows NT
Author:
Neil Hodgson <neilh at scintilla.org>
Status:
Final
Type:
Standards Track
Created:
11-Jan-2002
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
Rationale
Specification
Restrictions
Reference Implementation
References
Copyright
Abstract
This... | Final | PEP 277 – Unicode file name support for Windows NT | Standards Track | This PEP discusses supporting access to all files possible on
Windows NT by passing Unicode file names directly to the system’s
wide-character functions. |
PEP 278 – Universal Newline Support
Author:
Jack Jansen <jack at cwi.nl>
Status:
Final
Type:
Standards Track
Created:
14-Jan-2002
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
Specification
Rationale
Reference Implementation
References
Copyright
Abstract
This PEP discusses a way in which Python ... | Final | PEP 278 – Universal Newline Support | Standards Track | This PEP discusses a way in which Python can support I/O on files
which have a newline format that is not the native format on the
platform, so that Python on each platform can read and import
files with CR (Macintosh), LF (Unix) or CR LF (Windows) line
endings. |
PEP 279 – The enumerate() built-in function
Author:
Raymond Hettinger <python at rcn.com>
Status:
Final
Type:
Standards Track
Created:
30-Jan-2002
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
Rationale
BDFL Pronouncements
Specification for a new built-in
Copyright
Abstract
This PEP introduces a... | Final | PEP 279 – The enumerate() built-in function | Standards Track | This PEP introduces a new built-in function, enumerate() to
simplify a commonly used looping idiom. It provides all iterable
collections with the same advantage that iteritems() affords to
dictionaries – a compact, readable, reliable index notation. |
PEP 280 – Optimizing access to globals
Author:
Guido van Rossum <guido at python.org>
Status:
Deferred
Type:
Standards Track
Created:
10-Feb-2002
Python-Version:
2.3
Post-History:
Table of Contents
Deferral
Abstract
Description
Additional Ideas
FAQs
Graphics
Comparison
Copyright
Deferral
While this PEP is a ni... | Deferred | PEP 280 – Optimizing access to globals | Standards Track | This PEP describes yet another approach to optimizing access to
module globals, providing an alternative to PEP 266 (Optimizing
Global Variable/Attribute Access by Skip Montanaro) and PEP 267
(Optimized Access to Module Namespaces by Jeremy Hylton). |
PEP 281 – Loop Counter Iteration with range and xrange
Author:
Magnus Lie Hetland <magnus at hetland.org>
Status:
Rejected
Type:
Standards Track
Created:
11-Feb-2002
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
Pronouncement
Motivation
Specification
Alternatives
Backwards Compatibility
Copyright
... | Rejected | PEP 281 – Loop Counter Iteration with range and xrange | Standards Track | This PEP describes yet another way of exposing the loop counter in
for-loops. It basically proposes that the functionality of the
function indices() from PEP 212 be included in the existing
functions range() and xrange(). |
PEP 282 – A Logging System
Author:
Vinay Sajip <vinay_sajip at red-dove.com>,
Trent Mick <trentm at activestate.com>
Status:
Final
Type:
Standards Track
Created:
04-Feb-2002
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
Motivation
Influences
Simple Example
Control Flow
Levels
Loggers
Handlers
LogRe... | Final | PEP 282 – A Logging System | Standards Track | This PEP describes a proposed logging package for Python’s
standard library. |
PEP 283 – Python 2.3 Release Schedule
Author:
Guido van Rossum
Status:
Final
Type:
Informational
Topic:
Release
Created:
27-Feb-2002
Python-Version:
2.3
Post-History:
27-Feb-2002
Table of Contents
Abstract
Release Manager
Completed features for 2.3
Planned features for 2.3
Ongoing tasks
Open issues
Features that d... | Final | PEP 283 – Python 2.3 Release Schedule | Informational | This document describes the development and release schedule for
Python 2.3. 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 284 – Integer for-loops
Author:
David Eppstein <eppstein at ics.uci.edu>,
Gregory Ewing <greg.ewing at canterbury.ac.nz>
Status:
Rejected
Type:
Standards Track
Created:
01-Mar-2002
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
Pronouncement
Rationale
Specification
Issues
Implementation
Referenc... | Rejected | PEP 284 – Integer for-loops | Standards Track | This PEP proposes to simplify iteration over intervals of
integers, by extending the range of expressions allowed after a
“for” keyword to allow three-way comparisons such as |
PEP 285 – Adding a bool type
Author:
Guido van Rossum <guido at python.org>
Status:
Final
Type:
Standards Track
Created:
08-Mar-2002
Python-Version:
2.3
Post-History:
08-Mar-2002, 30-Mar-2002, 03-Apr-2002
Table of Contents
Abstract
Review
Rationale
Specification
C API
Clarification
Compatibility
Resolved Issues
Im... | Final | PEP 285 – Adding a bool type | Standards Track | This PEP proposes the introduction of a new built-in type, bool,
with two constants, False and True. The bool type would be a
straightforward subtype (in C) of the int type, and the values
False and True would behave like 0 and 1 in most respects (for
example, False==0 and True==1 would be true) except repr() and
str(... |
PEP 286 – Enhanced Argument Tuples
Author:
Martin von Löwis <martin at v.loewis.de>
Status:
Deferred
Type:
Standards Track
Created:
03-Mar-2002
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
PEP Deferral
Problem description
Proposed solution
Affected converters
New converters
References
Copyright
... | Deferred | PEP 286 – Enhanced Argument Tuples | Standards Track | PyArg_ParseTuple is confronted with difficult memory management if
an argument converter creates new memory. To deal with these
cases, a specialized argument type is proposed. |
PEP 288 – Generators Attributes and Exceptions
Author:
Raymond Hettinger <python at rcn.com>
Status:
Withdrawn
Type:
Standards Track
Created:
21-Mar-2002
Python-Version:
2.5
Post-History:
Table of Contents
Abstract
Status
Rationale
Specification for Generator Attributes
Specification for Generator Exception Passi... | Withdrawn | PEP 288 – Generators Attributes and Exceptions | Standards Track | This PEP proposes to enhance generators by providing mechanisms for
raising exceptions and sharing data with running generators. |
PEP 289 – Generator Expressions
Author:
Raymond Hettinger <python at rcn.com>
Status:
Final
Type:
Standards Track
Created:
30-Jan-2002
Python-Version:
2.4
Post-History:
22-Oct-2003
Table of Contents
Abstract
Rationale
BDFL Pronouncements
The Details
Early Binding versus Late Binding
Reduction Functions
Acknowledge... | Final | PEP 289 – Generator Expressions | Standards Track | This PEP introduces generator expressions as a high performance,
memory efficient generalization of list comprehensions PEP 202 and
generators PEP 255. |
PEP 290 – Code Migration and Modernization
Author:
Raymond Hettinger <python at rcn.com>
Status:
Active
Type:
Informational
Created:
06-Jun-2002
Post-History:
Table of Contents
Abstract
Rationale
Guidelines for New Entries
Migration Issues
Comparison Operators Not a Shortcut for Producing 0 or 1
Modernization P... | Active | PEP 290 – Code Migration and Modernization | Informational | This PEP is a collection of procedures and ideas for updating Python
applications when newer versions of Python are installed. |
PEP 291 – Backward Compatibility for the Python 2 Standard Library
Author:
Neal Norwitz <nnorwitz at gmail.com>
Status:
Final
Type:
Informational
Created:
06-Jun-2002
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
Rationale
Features to Avoid
Backward Compatible Packages, Modules, and Tools
Notes
C... | Final | PEP 291 – Backward Compatibility for the Python 2 Standard Library | Informational | This PEP describes the packages and modules in the Python 2
standard library which should remain backward compatible with
previous versions of Python. If a package is not listed here,
then it need only remain compatible with the version of Python it
is distributed with. |
PEP 292 – Simpler String Substitutions
Author:
Barry Warsaw <barry at python.org>
Status:
Final
Type:
Standards Track
Created:
18-Jun-2002
Python-Version:
2.4
Post-History:
18-Jun-2002, 23-Mar-2004, 22-Aug-2004
Replaces:
215
Table of Contents
Abstract
Rationale
A Simpler Proposal
Why $ and Braces?
Comparison to PE... | Final | PEP 292 – Simpler String Substitutions | Standards Track | This PEP describes a simpler string substitution feature, also
known as string interpolation. This PEP is “simpler” in two
respects: |
PEP 293 – Codec Error Handling Callbacks
Author:
Walter Dörwald <walter at livinglogic.de>
Status:
Final
Type:
Standards Track
Created:
18-Jun-2002
Python-Version:
2.3
Post-History:
19-Jun-2002
Table of Contents
Abstract
Specification
Rationale
Implementation Notes
Backwards Compatibility
References
Copyright
A... | Final | PEP 293 – Codec Error Handling Callbacks | Standards Track | This PEP aims at extending Python’s fixed codec error handling
schemes with a more flexible callback based approach. |
PEP 294 – Type Names in the types Module
Author:
Oren Tirosh <oren at hishome.net>
Status:
Rejected
Type:
Standards Track
Created:
19-Jun-2002
Python-Version:
2.5
Post-History:
Table of Contents
Abstract
Pronouncement
Rationale
Specification
Backward compatibility
Reference Implementation
Copyright
Abstract
Th... | Rejected | PEP 294 – Type Names in the types Module | Standards Track | This PEP proposes that symbols matching the type name should be added
to the types module for all basic Python types in the types module: |
PEP 295 – Interpretation of multiline string constants
Author:
Stepan Koltsov <yozh at mx1.ru>
Status:
Rejected
Type:
Standards Track
Created:
22-Jul-2002
Python-Version:
3.0
Post-History:
Table of Contents
Abstract
Rationale
Implementation
Alternatives
Copyright
Abstract
This PEP describes an interpretation o... | Rejected | PEP 295 – Interpretation of multiline string constants | Standards Track | This PEP describes an interpretation of multiline string constants
for Python. It suggests stripping spaces after newlines and
stripping a newline if it is first character after an opening
quotation. |
PEP 296 – Adding a bytes Object Type
Author:
Scott Gilbert <xscottg at yahoo.com>
Status:
Withdrawn
Type:
Standards Track
Created:
12-Jul-2002
Python-Version:
2.3
Post-History:
Table of Contents
Notice
Abstract
Rationale
Specification
Contrast to existing types
Backward Compatibility
Reference Implementation
Addi... | Withdrawn | PEP 296 – Adding a bytes Object Type | Standards Track | This PEP proposes the creation of a new standard type and builtin
constructor called ‘bytes’. The bytes object is an efficiently
stored array of bytes with some additional characteristics that
set it apart from several implementations that are similar. |
PEP 297 – Support for System Upgrades
Author:
Marc-André Lemburg <mal at lemburg.com>
Status:
Rejected
Type:
Standards Track
Created:
19-Jul-2001
Python-Version:
2.6
Post-History:
Table of Contents
Rejection Notice
Abstract
Problem
Proposed Solutions
Scope
Credits
References
Copyright
Rejection Notice
This PEP... | Rejected | PEP 297 – Support for System Upgrades | Standards Track | This PEP proposes strategies to allow the Python standard library
to be upgraded in parts without having to reinstall the complete
distribution or having to wait for a new patch level release. |
PEP 298 – The Locked Buffer Interface
Author:
Thomas Heller <theller at python.net>
Status:
Withdrawn
Type:
Standards Track
Created:
26-Jul-2002
Python-Version:
2.3
Post-History:
30-Jul-2002, 01-Aug-2002
Table of Contents
Abstract
Specification
Implementation
Backward Compatibility
Reference Implementation
Additio... | Withdrawn | PEP 298 – The Locked Buffer Interface | Standards Track | This PEP proposes an extension to the buffer interface called the
‘locked buffer interface’. |
PEP 299 – Special __main__() function in modules
Author:
Jeff Epler <jepler at unpythonic.net>
Status:
Rejected
Type:
Standards Track
Created:
12-Aug-2002
Python-Version:
2.3
Post-History:
29-Mar-2006
Table of Contents
Abstract
Motivation
Proposal
Implementation
Open Issues
Rejection
References
Copyright
Abstra... | Rejected | PEP 299 – Special __main__() function in modules | Standards Track | Many Python modules are also intended to be callable as standalone
scripts. This PEP proposes that a special function called __main__()
should serve this purpose. |
PEP 301 – Package Index and Metadata for Distutils
Author:
Richard Jones <richard at python.org>
Status:
Final
Type:
Standards Track
Topic:
Packaging
Created:
24-Oct-2002
Python-Version:
2.3
Post-History:
08-Nov-2002
Table of Contents
Abstract
Rationale
Specification
Web Interface
User Roles
Index Storage (Schema)... | Final | PEP 301 – Package Index and Metadata for Distutils | Standards Track | This PEP proposes several extensions to the Distutils packaging system
[1]. These enhancements include a central package index server,
tools for submitting package information to the index and extensions
to the package metadata to include Trove [2] information. |
PEP 302 – New Import Hooks
Author:
Just van Rossum <just at letterror.com>,
Paul Moore <p.f.moore at gmail.com>
Status:
Final
Type:
Standards Track
Created:
19-Dec-2002
Python-Version:
2.3
Post-History:
19-Dec-2002
Table of Contents
Abstract
Motivation
Use cases
Rationale
Specification part 1: The Importer Protoco... | Final | PEP 302 – New Import Hooks | Standards Track | This PEP proposes to add a new set of import hooks that offer better
customization of the Python import mechanism. Contrary to the current
__import__ hook, a new-style hook can be injected into the existing
scheme, allowing for a finer grained control of how modules are found and how
they are loaded. |
PEP 303 – Extend divmod() for Multiple Divisors
Author:
Thomas Bellman <bellman+pep-divmod at lysator.liu.se>
Status:
Rejected
Type:
Standards Track
Created:
31-Dec-2002
Python-Version:
2.3
Post-History:
Table of Contents
Abstract
Pronouncement
Specification
Motivation
Rationale
Backwards Compatibility
Reference ... | Rejected | PEP 303 – Extend divmod() for Multiple Divisors | Standards Track | This PEP describes an extension to the built-in divmod() function,
allowing it to take multiple divisors, chaining several calls to
divmod() into one. |
PEP 304 – Controlling Generation of Bytecode Files
Author:
Skip Montanaro
Status:
Withdrawn
Type:
Standards Track
Created:
22-Jan-2003
Post-History:
27-Jan-2003, 31-Jan-2003, 17-Jun-2005
Table of Contents
Historical Note
Abstract
Proposal
Glossary
Locating bytecode files
Writing bytecode files
Defining augmented d... | Withdrawn | PEP 304 – Controlling Generation of Bytecode Files | Standards Track | This PEP outlines a mechanism for controlling the generation and
location of compiled Python bytecode files. This idea originally
arose as a patch request [1] and evolved into a discussion thread on
the python-dev mailing list [2]. The introduction of an environment
variable will allow people installing Python or Pyt... |
PEP 306 – How to Change Python’s Grammar
Author:
Michael Hudson <mwh at python.net>, Jack Diederich <jackdied at gmail.com>, Alyssa Coghlan <ncoghlan at gmail.com>, Benjamin Peterson <benjamin at python.org>
Status:
Withdrawn
Type:
Informational
Created:
29-Jan-2003
Post-History:
30-Jan-2003
Table of Contents
Note... | Withdrawn | PEP 306 – How to Change Python’s Grammar | Informational | There’s more to changing Python’s grammar than editing
Grammar/Grammar and Python/compile.c. This PEP aims to be a
checklist of places that must also be fixed. |
PEP 309 – Partial Function Application
Author:
Peter Harris <scav at blueyonder.co.uk>
Status:
Final
Type:
Standards Track
Created:
08-Feb-2003
Python-Version:
2.5
Post-History:
10-Feb-2003, 27-Feb-2003, 22-Feb-2004, 28-Apr-2006
Table of Contents
Note
Abstract
Acceptance
Motivation
Example Implementation
Examples ... | Final | PEP 309 – Partial Function Application | Standards Track | This proposal is for a function or callable class that allows a new
callable to be constructed from a callable and a partial argument list
(including positional and keyword arguments). |
PEP 310 – Reliable Acquisition/Release Pairs
Author:
Michael Hudson <mwh at python.net>,
Paul Moore <p.f.moore at gmail.com>
Status:
Rejected
Type:
Standards Track
Created:
18-Dec-2002
Python-Version:
2.4
Post-History:
Table of Contents
Abstract
Pronouncement
Rationale
Basic Syntax and Semantics
Possible Extensio... | Rejected | PEP 310 – Reliable Acquisition/Release Pairs | Standards Track | It would be nice to have a less typing-intense way of writing: |
PEP 311 – Simplified Global Interpreter Lock Acquisition for Extensions
Author:
Mark Hammond <mhammond at skippinet.com.au>
Status:
Final
Type:
Standards Track
Created:
05-Feb-2003
Python-Version:
2.3
Post-History:
05-Feb-2003, 14-Feb-2003, 19-Apr-2003
Table of Contents
Abstract
Rationale
Limitations and Exclusion... | Final | PEP 311 – Simplified Global Interpreter Lock Acquisition for Extensions | Standards Track | This PEP proposes a simplified API for access to the Global
Interpreter Lock (GIL) for Python extension modules.
Specifically, it provides a solution for authors of complex
multi-threaded extensions, where the current state of Python
(i.e., the state of the GIL is unknown. |
PEP 312 – Simple Implicit Lambda
Author:
Roman Suzi <rnd at onego.ru>, Alex Martelli <aleaxit at gmail.com>
Status:
Deferred
Type:
Standards Track
Created:
11-Feb-2003
Python-Version:
2.4
Post-History:
Table of Contents
Abstract
Deferral
Motivation
Rationale
Syntax
Examples of Use
Implementation
Discussion
Credit... | Deferred | PEP 312 – Simple Implicit Lambda | Standards Track | This PEP proposes to make argumentless lambda keyword optional in
some cases where it is not grammatically ambiguous. |
PEP 313 – Adding Roman Numeral Literals to Python
Author:
Mike Meyer <mwm at mired.org>
Status:
Rejected
Type:
Standards Track
Created:
01-Apr-2003
Python-Version:
2.4
Post-History:
Table of Contents
Abstract
BDFL Pronouncement
Rationale
Syntax for Roman literals
Built-In “roman” Function
Compatibility Issues
Cop... | Rejected | PEP 313 – Adding Roman Numeral Literals to Python | Standards Track | This PEP (also known as PEP CCCXIII) proposes adding Roman
numerals as a literal type. It also proposes the new built-in
function “roman”, which converts an object to an integer, then
converts the integer to a string that is the Roman numeral literal
equivalent to the integer. |
PEP 315 – Enhanced While Loop
Author:
Raymond Hettinger <python at rcn.com>, W Isaac Carroll <icarroll at pobox.com>
Status:
Rejected
Type:
Standards Track
Created:
25-Apr-2003
Python-Version:
2.5
Post-History:
Table of Contents
Abstract
Notice
Motivation
Syntax
Semantics of break and continue
Future Statement
Im... | Rejected | PEP 315 – Enhanced While Loop | Standards Track | This PEP proposes adding an optional “do” clause to the beginning
of the while loop to make loop code clearer and reduce errors
caused by code duplication. |
PEP 316 – Programming by Contract for Python
Author:
Terence Way <terry at wayforward.net>
Status:
Deferred
Type:
Standards Track
Created:
02-May-2003
Post-History:
Table of Contents
Abstract
Motivation
Specification
Exceptions
Inheritance
Rationale
Reference Implementation
References
Copyright
Abstract
This... | Deferred | PEP 316 – Programming by Contract for Python | Standards Track | This submission describes programming by contract for Python.
Eiffel’s Design By Contract(tm) is perhaps the most popular use of
programming contracts [2]. |
PEP 317 – Eliminate Implicit Exception Instantiation
Author:
Steven Taschuk <staschuk at telusplanet.net>
Status:
Rejected
Type:
Standards Track
Created:
06-May-2003
Python-Version:
2.4
Post-History:
09-Jun-2003
Table of Contents
Abstract
Motivation
String Exceptions
Implicit Instantiation
Specification
Backward... | Rejected | PEP 317 – Eliminate Implicit Exception Instantiation | Standards Track | —Guido van Rossum, in 1997 [1] |
PEP 318 – Decorators for Functions and Methods
Author:
Kevin D. Smith <Kevin.Smith at theMorgue.org>, Jim J. Jewett, Skip Montanaro, Anthony Baxter
Status:
Final
Type:
Standards Track
Created:
05-Jun-2003
Python-Version:
2.4
Post-History:
09-Jun-2003, 10-Jun-2003, 27-Feb-2004, 23-Mar-2004, 30-Aug-2004,
02-Sep-2004
... | Final | PEP 318 – Decorators for Functions and Methods | Standards Track | The current method for transforming functions and methods (for instance,
declaring them as a class or static method) is awkward and can lead to
code that is difficult to understand. Ideally, these transformations
should be made at the same point in the code where the declaration
itself is made. This PEP introduces ne... |
PEP 319 – Python Synchronize/Asynchronize Block
Author:
Michel Pelletier <michel at users.sourceforge.net>
Status:
Rejected
Type:
Standards Track
Created:
24-Feb-2003
Python-Version:
2.4
Post-History:
Table of Contents
Abstract
Pronouncement
Synchronization Targets
Other Patterns that Synchronize
Formal Syntax
Pr... | Rejected | PEP 319 – Python Synchronize/Asynchronize Block | Standards Track | This PEP proposes adding two new keywords to Python, ‘synchronize’
and ‘asynchronize’. |
PEP 320 – Python 2.4 Release Schedule
Author:
Barry Warsaw, Raymond Hettinger, Anthony Baxter
Status:
Final
Type:
Informational
Topic:
Release
Created:
29-Jul-2003
Python-Version:
2.4
Post-History:
01-Dec-2004
Table of Contents
Abstract
Release Manager
Release Schedule
Completed features for 2.4
Deferred until 2.5... | Final | PEP 320 – Python 2.4 Release Schedule | Informational | This document describes the development and release schedule for
Python 2.4. 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 321 – Date/Time Parsing and Formatting
Author:
A.M. Kuchling <amk at amk.ca>
Status:
Withdrawn
Type:
Standards Track
Created:
16-Sep-2003
Python-Version:
2.4
Post-History:
Table of Contents
Abstract
Input Formats
Generic Input Parsing
Output Formats
References
Copyright
Abstract
Python 2.3 added a number o... | Withdrawn | PEP 321 – Date/Time Parsing and Formatting | Standards Track | Python 2.3 added a number of simple date and time types in the
datetime module. There’s no support for parsing strings in various
formats and returning a corresponding instance of one of the types.
This PEP proposes adding a family of predefined parsing function for
several commonly used date and time formats, and a f... |
PEP 322 – Reverse Iteration
Author:
Raymond Hettinger <python at rcn.com>
Status:
Final
Type:
Standards Track
Created:
24-Sep-2003
Python-Version:
2.4
Post-History:
24-Sep-2003
Table of Contents
Abstract
Motivation
Proposal
BDFL Pronouncement
Alternative Method Names
Discussion
Real World Use Cases
Rejected Altern... | Final | PEP 322 – Reverse Iteration | Standards Track | This proposal is to add a builtin function to support reverse
iteration over sequences. |
PEP 323 – Copyable Iterators
Author:
Alex Martelli <aleaxit at gmail.com>
Status:
Deferred
Type:
Standards Track
Created:
25-Oct-2003
Python-Version:
2.5
Post-History:
29-Oct-2003
Table of Contents
Deferral
Abstract
Update and Comments
Motivation
Specification
Details
Rationale
References
Copyright
Deferral
Thi... | Deferred | PEP 323 – Copyable Iterators | Standards Track | This PEP suggests that some iterator types should support shallow
copies of their instances by exposing a __copy__ method which meets
some specific requirements, and indicates how code using an iterator
might exploit such a __copy__ method when present. |
PEP 324 – subprocess - New process module
Author:
Peter Astrand <astrand at lysator.liu.se>
Status:
Final
Type:
Standards Track
Created:
19-Nov-2003
Python-Version:
2.4
Post-History:
Table of Contents
Abstract
Motivation
Rationale
Specification
Exceptions
Security
Popen objects
Replacing older functions with th... | Final | PEP 324 – subprocess - New process module | Standards Track | This PEP describes a new module for starting and communicating
with processes. |
PEP 325 – Resource-Release Support for Generators
Author:
Samuele Pedroni <pedronis at python.org>
Status:
Rejected
Type:
Standards Track
Created:
25-Aug-2003
Python-Version:
2.4
Post-History:
Table of Contents
Abstract
Pronouncement
Rationale
Possible Semantics
Remarks
Open Issues
Alternative Ideas
Copyright
... | Rejected | PEP 325 – Resource-Release Support for Generators | Standards Track | Generators allow for natural coding and abstraction of traversal
over data. Currently if external resources needing proper timely
release are involved, generators are unfortunately not adequate.
The typical idiom for timely release is not supported, a yield
statement is not allowed in the try clause of a try-finally
s... |
PEP 326 – A Case for Top and Bottom Values
Author:
Josiah Carlson <jcarlson at uci.edu>,
Terry Reedy <tjreedy at udel.edu>
Status:
Rejected
Type:
Standards Track
Created:
20-Dec-2003
Python-Version:
2.4
Post-History:
20-Dec-2003, 03-Jan-2004, 05-Jan-2004, 07-Jan-2004,
21-Feb-2004
Table of Contents
Results
Abstract... | Rejected | PEP 326 – A Case for Top and Bottom Values | Standards Track | This PEP proposes two singleton constants that represent a top and
bottom [3] value: Max and Min (or two similarly suggestive
names [4]; see Open Issues). |
PEP 327 – Decimal Data Type
Author:
Facundo Batista <facundo at taniquetil.com.ar>
Status:
Final
Type:
Standards Track
Created:
17-Oct-2003
Python-Version:
2.4
Post-History:
30-Nov-2003, 02-Jan-2004, 29-Jan-2004
Table of Contents
Abstract
Motivation
The problem with binary float
Why floating point?
Why not rationa... | Final | PEP 327 – Decimal Data Type | Standards Track | The idea is to have a Decimal data type, for every use where decimals
are needed but binary floating point is too inexact. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.