iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updated timeline.

This commit is contained in:
Guido van Rossum 2006-12-19 21:17:06 +00:00
parent 7cbb1c2f19
commit 36fd009b8a
1 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
pep-3000.txt
View File

@ -48,10 +48,13 @@ Python 3000 before we started the Python 3000 process for real. PEP
Timeline
========
We need a meta-PEP for the Python 3000 timeline. At this moment, I
hope to have a first alpha release out sometime in 2007; it may take
another year after that (or more) before the first proper release,
named Python 3.0.
I no longer think we need a meta-PEP for the Python 3000 timeline;
instead, here's my current proposal. I hope to have a first alpha
release (3.0a1) out in the first half of 2007; it should take no more
than a year from then before the first proper release, named Python
3.0. I would like all PEPs for features going into Python 3000 to be
submitted by the end of April 2007 (allowing time for discussion and
implementation after the initial submission).
I expect that there will be parallel Python 2.x and 3.x releases for
some time; the Python 2.x releases will continue for a longer time
@ -63,9 +66,9 @@ releases even after 3.0 (final) has been released, probably well into
continued 2.x support, acceptance and stability of 3.0, and volunteer
stamina.
It's quite possible that Python 3.1 and 3.2 will be released much
sooner after 3.0 than has been customary for the 2.x series. The 3.x
release pattern will stabilize once the community is happy with 3.x.
I expect that Python 3.1 and 3.2 will be released much sooner after
3.0 than has been customary for the 2.x series. The 3.x release
pattern will stabilize once the community is happy with 3.x.
Compatibility and Transition