summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJeremy Hylton <jeremy@alum.mit.edu>2000-06-30 17:30:18 (GMT)
committerJeremy Hylton <jeremy@alum.mit.edu>2000-06-30 17:30:18 (GMT)
commit7efcafb994a5e97bf458b3138a7694a3c41b7ca7 (patch)
treebca24eafd38fbde03f84923aa61b987a21b8b8af
parenta0f3c5c8d533acc7e86a85eaf95d6d9175a178f9 (diff)
downloadcpython-7efcafb994a5e97bf458b3138a7694a3c41b7ca7.zip
cpython-7efcafb994a5e97bf458b3138a7694a3c41b7ca7.tar.gz
cpython-7efcafb994a5e97bf458b3138a7694a3c41b7ca7.tar.bz2
add note about what happened to Python 1.6
also, fix type (not caught by Rob Hooft, but could have been :-)
-rw-r--r--README6
1 files changed, 5 insertions, 1 deletions
diff --git a/README b/README
index 7bdca09..b91e7e5 100644
--- a/README
+++ b/README
@@ -20,7 +20,11 @@ incrementing, that same quality makes parts of the rest of the world
think that Python is barely out of its first alpha test. Especially
enterprise customers are often fearful of anything that's version 1.x!
The new version number also clearly marks departure of Python's core
-development teal from CNRI to join BeOpen.com.
+development team from CNRI to join BeOpen.com.
+
+What happened to Python 1.6? It was promoted and renamed Python 2.0.
+There were two alpha releases of Python 1.6 before we decided to
+increment the major version number.
Previously, the version number 2.0 was associated with a mythical and
elusive incompatible future release. That release (still ways off,