Mark PEP 479 as accepted and clarify the process.
This commit is contained in:
parent
0b62636a1b
commit
6037436ec8
18
pep-0479.txt
18
pep-0479.txt
|
@ -3,12 +3,12 @@ Title: Change StopIteration handling inside generators
|
|||
Version: $Revision$
|
||||
Last-Modified: $Date$
|
||||
Author: Chris Angelico <rosuav@gmail.com>, Guido van Rossum <guido@python.org>
|
||||
Status: Draft
|
||||
Status: Accepted
|
||||
Type: Standards Track
|
||||
Content-Type: text/x-rst
|
||||
Created: 15-Nov-2014
|
||||
Python-Version: 3.5
|
||||
Post-History: 15-Nov-2014, 19-Nov-2014
|
||||
Post-History: 15-Nov-2014, 19-Nov-2014, 5-Dec-2014
|
||||
|
||||
|
||||
Abstract
|
||||
|
@ -22,6 +22,20 @@ incompatible, the feature is initially introduced using a
|
|||
``__future__`` statement.
|
||||
|
||||
|
||||
Acceptance
|
||||
==========
|
||||
|
||||
This PEP was accepted by the BDFL on November 22. Because of the
|
||||
exceptionally short period from first draft to acceptance, the main
|
||||
objections brought up after acceptance were carefully considered and
|
||||
have been reflected in the "Alternate proposals" section below.
|
||||
However, none of the discussion changed the BDFL's mind and the PEP's
|
||||
acceptance is now final. (Suggestions for clarifying edits are still
|
||||
welcome -- unlike IETF RFCs, the text of a PEP is not cast in stone
|
||||
after its acceptance, although the core design/plan/specification
|
||||
should not change after acceptance.)
|
||||
|
||||
|
||||
Rationale
|
||||
=========
|
||||
|
||||
|
|
Loading…
Reference in New Issue