The History of Python: A Brief Timeline of Python http://python-history.blogspot.in/2009/01/brief-timeline-of-python.

html

More Next Blog» Create Blog Sign In

The History of Python

A series of articles on the history of the Python programming language and its community.

Tuesday, January 20, 2009

Followers
A Brief Timeline of Python

The development of Python occurred at a time when many other Followers (1218) Next
dynamic (and open-source) programming languages such as Tcl,
Perl, and (much later) Ruby were also being actively developed
and gaining popularity. To help put Python in its proper historical
perspective, the following list shows the release history of Python.
The earliest dates are approximate as I didn't consistently record
all events:

Release Date Version Follow

December, 1989 Implementation started
1990 Internal releases at CWI
Blog Archive
February 20, 1991 0.9.0 (released to alt.sources)
February, 1991 0.9.1 ► 2013 (4)
► 2011 (1)
Autumn, 1991 0.9.2
► 2010 (7)
December 24, 1991 0.9.4 ▼ 2009 (19)
January 2, 1992 0.9.5 (Macintosh only) ► April (4)
► March (5)
April 6, 1992 0.9.6
► February (4)
Unknown, 1992 0.9.7beta ▼ January (6)
January 9, 1993 0.9.8 Microsoft Ships Python Code... in 1996

July 29, 1993 0.9.9 Personal History - part 2, CNRI and

beyond
January 26, 1994 1.0.0 Personal History - part 1, CWI
February 15, 1994 1.0.2 A Brief Timeline of Python

May 4, 1994 1.0.3 Python's Design Philosophy

Introduction and Overview
July 14, 1994 1.0.4
October 11, 1994 1.1
November 10, 1994 1.1.1 About Me
April 13, 1995 1.2
Guido van Rossum
October 13, 1995 1.3
October 25, 1996 1.4
January 3, 1998 1.5
October 31, 1998 1.5.1
Python's BDFL
April 13, 1999 1.5.2
View my complete profile
September 5, 2000 1.6
October 16, 2000 2.0
April 17, 2001 2.1
December 21, 2001 2.2
July 29, 2003 2.3
November 30, 2004 2.4
September 16, 2006 2.5
October 1, 2008 2.6
December 3, 2008 3.0
I've added hyperlinks to the releases that are still being
advertised on python.org at this time. Note that many releases
were followed by several micro-releases, e.g. 2.0.1; I haven't
bothered to include these in the table as otherwise it would
become too long. Source tarball of very old releases are also still
accessible, here: http://www.python.org/ftp/python/src/. Various
ancient binary releases and other historical artefacts can still be
found by going one level up from there.
Posted by Guido van Rossum at 2:05 PM

1 of 3 Monday 08 January 2018 04:31 PM

The History of Python: A Brief Timeline of Python http://python-history.blogspot.in/2009/01/brief-timeline-of-python.html

6 comments:

Chris January 20, 2009 at 5:38 PM

I think the coolest way to visualize Python's history is through

code_swarm:

http://www.vimeo.com/1093745

Reply

Juanjo Conti January 21, 2009 at 12:00 PM

Spanish translation: here.

Reply

Uzah January 26, 2009 at 8:31 PM

a) how long did it take you to realize the "range" function is using huge
amounts of memory when used in a for loop ? Did you not envison
people needing more than a few iterations ? If there should only be one
way to do something, why have both range and xrange ?

b) When are you going to add File.open ?

c) how many more special reserved words are you going to use for
"built-in" functions, and are there going to be any "free" names left for
people to use in their programs without fear of conflict ?

d) how many more upgy underscore methods are you going to hack into
the "language" ?

e) why is everything about this "language" so hacky and provide a

million different ways to do the same thing (get/getattr/hasattr/has_key
/in/etc) ?

f) Is the motivation behind the "property" function/decorator/object? to

win the most stupid syntax ever ?

when are you going

Reply

Alok January 28, 2009 at 8:34 PM

Wish all these subversion repositories would quickly move onto a DVCS,
like git.

Tired of using $ git svn, to slowly painfully accumulate history.

Reply

verte January 29, 2009 at 5:53 PM

@Uzah:

b) what's wrong with open() ? it could conceivably return more than files.
in 3.0, it returns an io.BufferedReader.

c) built in functions are not reserved words. you can define your own
function called open, and you can use a local variable called open
without any problems.

d) ugly underscore methods? methods of what? what are you talking

about?

e) they all do very different things (except for has_key, which is going
away).

f) it's nice precisely because it doesn't introduce new syntax.

Reply

Guido van Rossum July 13, 2009 at 1:06 PM

Uzah, when will you stop beating your wife?

Reply

2 of 3 Monday 08 January 2018 04:31 PM

The History of Python: A Brief Timeline of Python http://python-history.blogspot.in/2009/01/brief-timeline-of-python.html

Enter your comment...

Comment as: Google Account

Publish Preview

Note: Only a member of this blog may post a comment.

Newer Post Home Older Post

Subscribe to: Post Comments (Atom)

3 of 3 Monday 08 January 2018 04:31 PM