Clarify the time covered by the moratorium. Also explicitly say an
extension would require another PEP.
This commit is contained in:
parent
04c67f605b
commit
6b527997a9
11
pep-3003.txt
11
pep-3003.txt
|
@ -15,7 +15,10 @@ Abstract
|
|||
|
||||
This PEP proposes a temporary moratorium (suspension) of all changes
|
||||
to the Python language syntax, semantics, and built-ins for a period
|
||||
of at least two years from the release of Python 3.1.
|
||||
of at least two years from the release of Python 3.1. In particular, the
|
||||
moratorium would include Python 3.2 (to be released 18-24 months after
|
||||
3.1) but allow Python 3.3 (assuming it is not released prematurely) to
|
||||
once again include language changes.
|
||||
|
||||
This suspension of features is designed to allow non-CPython implementations
|
||||
to "catch up" to the core implementation of the language, help ease adoption
|
||||
|
@ -133,6 +136,12 @@ A review of the NEWS file for the py3k development branch showed no
|
|||
commits would need to be rolled back in order to meet this goal.
|
||||
|
||||
|
||||
Extensions
|
||||
==========
|
||||
|
||||
The time period of the moratorium can only be extended through a new PEP.
|
||||
|
||||
|
||||
Copyright
|
||||
=========
|
||||
|
||||
|
|
Loading…
Reference in New Issue