Mass deferral as proposed on python-dev
This commit is contained in:
parent
f40dab2cec
commit
2e08612ea3
12
pep-0286.txt
12
pep-0286.txt
|
@ -3,7 +3,7 @@ Title: Enhanced Argument Tuples
|
|||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: martin@v.loewis.de (Martin von Löwis)
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Standards Track
|
||||
Created: 3-Mar-2002
|
||||
Python-Version: 2.3
|
||||
|
@ -16,6 +16,16 @@ Abstract
|
|||
an argument converter creates new memory. To deal with these
|
||||
cases, a specialized argument type is proposed.
|
||||
|
||||
PEP Deferral
|
||||
|
||||
Further exploration of the concepts covered in this PEP has been deferred
|
||||
for lack of a current champion interested in promoting the goals of the
|
||||
PEP and collecting and incorporating feedback, and with sufficient
|
||||
available time to do so effectively.
|
||||
|
||||
The resolution of this PEP may also be affected by the resolution of
|
||||
PEP 426, which proposes the use of a preprocessing step to generate
|
||||
some aspects of C API interface code.
|
||||
|
||||
Problem description
|
||||
|
||||
|
|
|
@ -3,7 +3,7 @@ Title: Logging Usage in the Standard Library
|
|||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: Michael P. Dubner <dubnerm@mindless.com>
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Standards Track
|
||||
Content-Type: text/plain
|
||||
Created: 02-Oct-2004
|
||||
|
@ -26,6 +26,13 @@ Abstract
|
|||
|
||||
logging.getLogger('py.BaseHTTPServer').setLevel(logging.FATAL)
|
||||
|
||||
PEP Deferral
|
||||
|
||||
Further exploration of the concepts covered in this PEP has been deferred
|
||||
for lack of a current champion interested in promoting the goals of the
|
||||
PEP and collecting and incorporating feedback, and with sufficient
|
||||
available time to do so effectively.
|
||||
|
||||
|
||||
Rationale
|
||||
|
||||
|
|
|
@ -3,7 +3,7 @@ Title: Standard image protocol and class
|
|||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: Lino Mastrodomenico <l.mastrodomenico@gmail.com>
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Standards Track
|
||||
Content-Type: text/x-rst
|
||||
Created: 28-Jun-2007
|
||||
|
@ -39,6 +39,13 @@ image manipulation functionality and implements the new protocol is
|
|||
also proposed, together with a mixin class that helps adding support
|
||||
for the protocol to existing image classes.
|
||||
|
||||
PEP Deferral
|
||||
============
|
||||
|
||||
Further exploration of the concepts covered in this PEP has been deferred
|
||||
for lack of a current champion interested in promoting the goals of the PEP
|
||||
and collecting and incorporating feedback, and with sufficient available
|
||||
time to do so effectively.
|
||||
|
||||
Rationale
|
||||
=========
|
||||
|
|
|
@ -3,7 +3,7 @@ Title: Module Version Numbers
|
|||
Version: $Revision: 65628 $
|
||||
Last-Modified: $Date: 2008-08-10 09:59:20 -0400 (Sun, 10 Aug 2008) $
|
||||
Author: Barry Warsaw <barry@python.org>
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Informational
|
||||
Content-Type: text/x-rst
|
||||
Created: 2011-03-16
|
||||
|
@ -24,6 +24,13 @@ Conformance with this PEP is optional, however other Python tools
|
|||
(such as ``distutils2`` [1]_) may be adapted to use the conventions
|
||||
defined here.
|
||||
|
||||
PEP Deferral
|
||||
============
|
||||
|
||||
Further exploration of the concepts covered in this PEP has been deferred
|
||||
for lack of a current champion interested in promoting the goals of the PEP
|
||||
and collecting and incorporating feedback, and with sufficient available
|
||||
time to do so effectively.
|
||||
|
||||
User Stories
|
||||
============
|
||||
|
|
|
@ -3,7 +3,7 @@ Title: Deprecate codecs.StreamReader and codecs.StreamWriter
|
|||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: Victor Stinner <victor.stinner@gmail.com>
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Standards Track
|
||||
Content-Type: text/x-rst
|
||||
Created: 28-May-2011
|
||||
|
@ -25,6 +25,13 @@ introduced in Python 2.6 and 3.0 (see the `PEP 3116
|
|||
<http://www.python.org/dev/peps/pep-3116/>`_), and reimplemented in C in
|
||||
Python 2.7 and 3.1.
|
||||
|
||||
PEP Deferral
|
||||
============
|
||||
|
||||
Further exploration of the concepts covered in this PEP has been deferred
|
||||
for lack of a current champion interested in promoting the goals of the PEP
|
||||
and collecting and incorporating feedback, and with sufficient available
|
||||
time to do so effectively.
|
||||
|
||||
Motivation
|
||||
==========
|
||||
|
|
10
pep-0419.txt
10
pep-0419.txt
|
@ -3,7 +3,7 @@ Title: Protecting cleanup statements from interruptions
|
|||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: Paul Colomiets <paul@colomiets.name>
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Standards Track
|
||||
Content-Type: text/x-rst
|
||||
Created: 06-Apr-2012
|
||||
|
@ -16,6 +16,14 @@ Abstract
|
|||
This PEP proposes a way to protect Python code from being interrupted
|
||||
inside a finally clause or during context manager cleanup.
|
||||
|
||||
PEP Deferral
|
||||
============
|
||||
|
||||
Further exploration of the concepts covered in this PEP has been deferred
|
||||
for lack of a current champion interested in promoting the goals of the PEP
|
||||
and collecting and incorporating feedback, and with sufficient available
|
||||
time to do so effectively.
|
||||
|
||||
|
||||
Rationale
|
||||
=========
|
||||
|
|
|
@ -4,7 +4,7 @@ Version: $Revision$
|
|||
Last-Modified: $Date$
|
||||
Author: Benoit Bryon <benoit@marmelune.net>
|
||||
Discussions-To: <distutils-sig@python.org>
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Informational
|
||||
Content-Type: text/x-rst
|
||||
Created: 24-May-2012
|
||||
|
@ -28,6 +28,11 @@ It provides guidelines and recipes for distribution authors:
|
|||
`specific recipes for existing projects
|
||||
<#how-to-apply-naming-guidelines-on-existing-projects>`_.
|
||||
|
||||
PEP Deferral
|
||||
============
|
||||
|
||||
Further consideration of this PEP has been deferred at least until after
|
||||
PEP 426 (package metadata 2.0) and related updates have been resolved.
|
||||
|
||||
Terminology
|
||||
===========
|
||||
|
|
14
pep-0444.txt
14
pep-0444.txt
|
@ -5,7 +5,7 @@ Last-Modified: $Date$
|
|||
Author: Chris McDonough <chrism@plope.com>,
|
||||
Armin Ronacher <armin.ronacher@active-4.com>
|
||||
Discussions-To: Python Web-SIG <web-sig@python.org>
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Informational
|
||||
Content-Type: text/x-rst
|
||||
Created: 19-Jul-2010
|
||||
|
@ -18,6 +18,18 @@ This document specifies a proposed second-generation standard
|
|||
interface between web servers and Python web applications or
|
||||
frameworks.
|
||||
|
||||
PEP Deferral
|
||||
============
|
||||
|
||||
Further exploration of the concepts covered in this PEP has been deferred
|
||||
for lack of a current champion interested in promoting the goals of the PEP
|
||||
and collecting and incorporating feedback, and with sufficient available
|
||||
time to do so effectively.
|
||||
|
||||
Note that since this PEP was first created, PEP 3333 was created as a more
|
||||
incremental update that permitted use of WSGI on Python 3.2+. However, an
|
||||
alternative specification that furthers the Python 3 goals of a cleaner
|
||||
separation of binary and text data may still be valuable.
|
||||
|
||||
Rationale and Goals
|
||||
===================
|
||||
|
|
|
@ -4,7 +4,7 @@ Version: $Revision$
|
|||
Last-Modified: $Date$
|
||||
Author: Phillip J. Eby <pje@telecommunity.com>
|
||||
Discussions-To: Python 3000 List <python-3000@python.org>
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Standards Track
|
||||
Content-Type: text/x-rst
|
||||
Requires: 3107, 3115, 3119
|
||||
|
|
10
pep-3143.txt
10
pep-3143.txt
|
@ -3,7 +3,7 @@ Title: Standard daemon process library
|
|||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: Ben Finney <ben+python@benfinney.id.au>
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Standards Track
|
||||
Content-Type: text/x-rst
|
||||
Created: 2009-01-26
|
||||
|
@ -40,6 +40,14 @@ provides a simple interface to the task of becoming a daemon process.
|
|||
References
|
||||
Copyright
|
||||
|
||||
============
|
||||
PEP Deferral
|
||||
============
|
||||
|
||||
Further exploration of the concepts covered in this PEP has been deferred
|
||||
for lack of a current champion interested in promoting the goals of the PEP
|
||||
and collecting and incorporating feedback, and with sufficient available
|
||||
time to do so effectively.
|
||||
|
||||
=============
|
||||
Specification
|
||||
|
|
|
@ -3,7 +3,7 @@ Title: Asynchronous I/O For subprocess.Popen
|
|||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: (James) Eric Pruitt, Charles R. McCreary, Josiah Carlson
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Standards Track
|
||||
Content-Type: text/plain
|
||||
Created: 04-Aug-2009
|
||||
|
@ -18,6 +18,13 @@ Abstract:
|
|||
subprocess.Popen more asynchronous to help alleviate these
|
||||
problems.
|
||||
|
||||
|
||||
PEP Deferral:
|
||||
|
||||
Further exploration of the concepts covered in this PEP has been deferred
|
||||
at least until after PEP 3156 has been resolved.
|
||||
|
||||
|
||||
Motivation:
|
||||
|
||||
A search for "python asynchronous subprocess" will turn up numerous
|
||||
|
|
|
@ -3,7 +3,7 @@ Title: Cofunctions
|
|||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: Gregory Ewing <greg.ewing@canterbury.ac.nz>
|
||||
Status: Draft
|
||||
Status: Deferred
|
||||
Type: Standards Track
|
||||
Content-Type: text/x-rst
|
||||
Created: 13-Feb-2009
|
||||
|
@ -27,6 +27,13 @@ it. However, it would be possible to define and implement cofunctions
|
|||
independently of PEP 380 if so desired.
|
||||
|
||||
|
||||
PEP Deferral
|
||||
============
|
||||
|
||||
Further exploration of the concepts covered in this PEP has been deferred
|
||||
at least until after PEP 3156 has been resolved.
|
||||
|
||||
|
||||
Specification
|
||||
=============
|
||||
|
||||
|
|
Loading…
Reference in New Issue